Process Apps → Working with Process Apps → Delivering Process Apps → Deploying a Process App
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:
The Deploy Process App dialog box opens.
See Deploy Process App Dialog Box for details.
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.
The Quick Deploy command lets you deploy a process app without being prompted to provide the information in the Deploy Process App dialog box.
To deploy a process app using the Quick Deploy command:
It is a good practice 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.
Clear this check box if you have finished your design work and want to use the Quick Deploy command to deploy the process app.
To use other deployment features:
Copyright © 2007–2015 Serena Software, Inc. All rights reserved.