SBM Path to Production and Patching Procedures

SBM Path to Production and Patching Procedures

Path-to-production-small.png   

In SBM, the "Path to Production" describes the steps you take to get design changes you make in Composer into your production environment.  The path to production used changes from system to system, often depending on number of users and other factors like the criticality of the process and the degree of oversight required before the production end-users see the changes.

The whitepaper linked below describes how larger customers who need complete control over deployment use Composer, Application Repository and the SBM Environments to move process apps and solutions from design to production. It describes both the standard mechanism of using Application Repository to transfer process apps between environments and an alternative sandbox approach, where two distinct SBM systems are used respectively for  (1) development, and (2) staging and production.

It also includes guidance on how to make patch changes in a production environment (i.e. changes outside of the development cycle for process apps), and how the different path to production topologies affect the approach you might take.

The whitepaper can be found here.

 If you enjoyed reading this blog entry, please subscribe to my blog by clicking the 'subscribe to updates from author' link below.

Labels (1)

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Comments
Thanks for this whitepaper. It would be cool if the execution of promotion could be automated via webservice (see idea http://www.serenacentral.com/community/ideas/sbm/ability-to-automate-promotion-of-a-process-app)
Hi Andreas, I can't make any promises, but I know folks are looking into that request. Tom
The useful information has been the targeted http://bestheadlightbulbs.net/
Hi Tom, Regarding the scientific sphere from the point of view of practical importance, I would like to bring new benefits to linguistics and software engineering. It goes without saying, that not everyone is able to reveal the unknown and cry “Eureka!” and not everyone is Einstein, but the key idea is not who you are but how much you are ready to give and sacrifice for the sake of progress. Hopefully, I have found the hook that can lead me to the depths of software engineering and linguistics. You may contact me to discuss the issue on http://writemypersonalstatement.net/personal-statement-help or Facebook - https://www.facebook.com/ashley.terr AT. Cheers, Ashley
Top Contributors
Version history
Revision #:
2 of 2
Last update:
‎2020-01-30 18:19
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.