Working with Process Apps → Deploying Process Apps → Deploying a Process App
Deploying a Process App
Before you can deploy a process app:
- You must have the
Deploy Process Apps privilege (set in
for on-premise customers) and the
Deploy privilege (set in the
- The process app must be stored in the repository. This means it has
been published from
SBM Composer, loaded from
a file, or imported as part of a solution file.
- Verify any endpoints and target servers that will be used by the
process app in the destination environment. In most cases, endpoints and target
servers are defined for you.
- If you are deploying the Global Process App (or any process app
that contains the Global Application) ensure that you are only deploying to an
environment in the same environment set from which it was originally loaded.
Process Apps tab, select the process app you
want to deploy.
Actions column, click the
Destination page, select the environment to
which you want to deploy the process app.
If there are application or orchestration endpoints that need
mapping, on the
Mappings page, perform the following steps:
Select an endpoint that does not have a destination.
From the list, select a destination endpoint or click
Create a new endpoint, and then provide
connection information for the new endpoint.
Repeat these steps for each endpoint as necessary.
Summary page displays the settings that you have
designated for the deploy.
The summary dialog box appears. Click
View Activity to see the status of the
deployment on the
Activities tab. Click the
Cancel icon to cancel the deployment if
necessary. You can select the
Terminate activity forcefully check box in the
Cancel Activity dialog box to force the running
process to stop, no matter what state it is in. In that case, no rollback
operations are performed.
Copyright © 2007–2018 Serena Software, Inc., a Micro Focus company. All rights reserved.