About Process App Distribution

Process apps have three output forms:

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 blueprints through:

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:

  • In Application Repository, you can deploy process apps that have been published or loaded from a file. This method is primarily used by organizations who want to closely monitory and control deployments to runtime environments and therefore do not allow deployments from SBM Composer.
  • In SBM Composer, you can deploy to environments where you have been granted permissions and where deployments from SBM Composer have been allowed. Use one of two methods:
    • Deploy

      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.

    • Quick Deploy

      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 with access 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.

Note: For more information about promotion and process app snapshots, see the SBM Application Repository Guide.

Related Topics

Publishing a Process App

Deploying a Process App

Modifying Locked Elements in a Published Process App