Process Apps → Working with Process Apps → Delivering Process Apps → Deploying a Process App

Deploying a Process App

Prerequisites:

Note: A process app must be published before it can be deployed. The publish operation is performed automatically when you deploy.

Use the Deploy or Quick Deploy command to make a process app available to users. See Using Quick Deploy for information about the second command.

To deploy a process app using the Deploy command:

  1. In the Quick Access Toolbar, click Deploy.

    The Deploy Process App dialog box opens.

  2. Perform the following steps:
    1. Select the environment to which you want to deploy.
    2. Type a version name, if you do not want to use the default value.
    3. Specify whether you want others to deploy the process app.

    See Deploy Process App Dialog Box for details.

  3. In the Deploy Options Dialog Box, set deployment options, such as a delayed start time, an e-mail notification, and whether to stop the deployment on warnings or only on errors.
  4. Map the process app endpoints to environment endpoints.

    Process app endpoints can be mapped to environment endpoints automatically using the initial configuration, but you can change the environment endpoint configuration as needed to deploy to different environments. Some process apps do not require endpoints.

    See New Environment Endpoint Dialog Box for details.

Note: If the process app you are deploying contains a report with the same name as an existing report in the target environment, and the two reports are in the same project, are stored in the same table, and have the same access level (for example, public or private), the deployment generates a warning about duplicate reports.
CAUTION:
If you deploy a process app that contains a Web service, and the defining .wsdl file contains an incorrect service location for the environment to which you deployed, you need to edit the endpoint in SBM Application Repository to point to the correct service location and then redeploy the process app so the changes can take effect. (You may also want to get the latest changes back to SBM Composer.)

If you then clone the environment and deploy the same process app to the cloned environment using default settings, the new deployment will not use the existing endpoints that you edited; it will instead create new endpoints with similar names. These new endpoints will contain the service location from the defining .wsdl file, so you need to edit them (as you did in the original environment) to point to the correct service location for the Web service. (Alternatively, you can edit the deployment in the Deploy Options Dialog Box in SBM Composer to use the correct endpoints and delete the duplicate ones.) In either case, you need to redeploy the process app to the cloned environment so these changes can take effect.

Using Quick Deploy

The Quick Deploy command enables you to deploy a process app without being prompted to provide the information in the Deploy Process App dialog box.

Note: If this is the first time you are deploying this process app, it is recommended that you use the Deploy command instead. The Deploy command enables you to see the default settings and change them, if necessary.

To deploy a process app using the Quick Deploy command:

  1. In the Quick Deploy area of the Deployment tab, clear the Create Versions of Process App Elements check box if you do not want to create process app versions in Application Repository.

    It is a good practice to clear this check box when you want to deploy and test a process app you are designing, but are not ready to commit your changes. This also prevents extraneous versions of the process app in the database.

    Select this check box if you are ready to commit your changes.

    Note: This check box cannot be cleared if the environment to which you are deploying does not have the Enable Development Deployment option selected in the Composer list in the Edit Environment dialog box in Application Repository.
  2. Select the Keep Design Elements Checked Out check box if you want design elements that were already checked out to remain checked out after the deployment. This eliminates the step of checking out design elements after you deploy, so you can continue to design.

    Clear this check box if you have finished your design work and want to use the Quick Deploy command to deploy the process app.

    Note: This check box is unavailable if the Create Versions of Process App Elements check box is cleared.
  3. In the Deploy To list, select the environment to which you want to deploy. You are prompted to map any unmapped endpoints that cannot be automatically mapped.
  4. Click Quick Deploy.
To determine the status of the deployment, look at the Message List, or right-click the process app name at the top of App Explorer, and select Get Deployment Status.

Using Other Deployment Features

After you perform a deployment, you might want to have SBM Work Center open automatically so you can see how the process app works, or open the SBM Work Center without doing a deployment. You also might want to open Application Repository to give other users permission to deploy the process app.

To use other deployment features:

  1. Click the Deployment tab on the Ribbon.
  2. In the Launch area of the tab, clear or select the Launch Work Center When Deployed check box to specify whether you want to open the SBM Work Center after the deployment completes.
  3. An application is selected in the Startup Application list. If you want to change it, select another one.
  4. Click Work Center to open SBM Work Center without performing a deployment. SBM Work Center opens to the application specified in the Open Application list, from the environment to which the process app was last deployed.
  5. Click Application Repository to open Application Repository.

Related Topics

About Process App Distribution

Using the Validation Results

Copyright © 2007–2019 Micro Focus or one of its affiliates. All rights reserved.