Process Apps → About Process Apps → Process Apps → About Process App Distribution
Represent a complete design of one or more applications, orchestrations, or both. Process app blueprints are created in SBM Composer, published to Application Repository, and deployed a runtime environment. When they are exported from SBM Composer, blueprints have an .msd file extension.
Blueprints can also be created in Application Repository by the "Get Process App from Application Engine" feature in the Environments area. You can then save this version of the process app to a file.
A type of process app that can be used a starting point for creating other process apps. For example, if you have some database fields that you want to include in every process app you create, you could create a template that includes those fields. For details, refer to About Templates.
Templates cannot be published or deployed, but they can be exported. When they are exported from SBM Composer, templates have an .mst file extension.
Contain both the blueprint information and configuration data, such as projects, notifications, and overrides defined in Application Administrator. Snapshots can be promoted from Application Repository to different environments, such as testing and production. When they are saved from Application Repository, snapshots have an .mss file extension. Snapshots are provided with Serena solutions, such as Serena Release Control and Serena Service Manager.
Blueprints and templates contain information about the version of SBM Composer they were developed in and exported from. You can import these files into the same or later version of SBM Composer, but not an earlier version.
You can distribute process app snapshots through Promotion.
You can distribute templates by converting process apps to templates, then exporting them to an .mst file.
Publishing packages process app created in SBM Composer and makes them available for deployment in Application Repository. You can publish a process app in one of the following ways:
For details, refer to Publishing a Process App.
Deployment makes process apps defined in SBM Composer available on the SBM Server. There are several ways to deploy process apps:
Use the full deployment method when you need to specify an environment, map endpoints, schedule deployments, and other default settings for a particular process app. When the deployment is completed, design elements are checked in. This method is recommended the first time you deploy a process app. For details, refer to Deploying a Process App.
Use this method to deploy a process app without being prompted to specify deployment settings. In addition, you can opt to deploy the process app without creating a new revision in the repository and to keep design elements checked out after a quick deploy so you can continue working in the process app. For more information, see Using Quick Deploy.
After a process app that contains an application is deployed, use SBM Application Administrator to create projects, add project-level overrides, and assign users and groups to the roles defined in SBM Composer.
Use the Export feature in SBM Composer to create a file version of a blueprint (.msd) that can be distributed outside of the Application Repository. The file can then be imported into SBM Composer or loaded into the Application Repository. For details, refer to Exporting a Process App.
You can also export template files (.mst).
Promotion enables administrators to Application Repository to replicate a process app from one environment to another. After deployment and testing, for example, a process app in the test environment can be replicated to the production environment. When you promote, you transfer both the process app design (created in SBM Composer) and the configuration data such as users, groups, notifications, and projects (set up in SBM Application Administrator) to another environment. The combination of design and configuration data is called a process app snapshot.
Copyright © 2007–2015 Serena Software, Inc. All rights reserved.