Configuring the Process Applications

This section describes how to configure an out-of-the-box default example. The details may be different depending on how you are customizing Development Manager for your processes.

The data that is imported with the snapshots includes a product called QLARIUS, and projects called JAVA_BRANCHA_STR, and MAINLINE_JAVA_STR.

If you are using the default QLARIUS product in Dimensions CM this will contain the correct data. If you are using a different product and/or projects, you will need to make sure it exists in Dimensions CM.

 

 

IMPORTANT!  When deploying the process apps you need to do so in the following order:

  1. Global Process App (eval)

  2. Dev Change Requests

  3. ALM Projects

  4. Dev Tasks

  5. Dev Packages

  6. Dev Control Orchestrations

  7. Quality Center Connector

If you receive an error when deploying a process app it is likely that it contains references to another process app that needs to be deployed before it.

 

 

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

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.

Related Topics:

Updating the Endpoints

Updating the Connection Details in the Workflows

Updating the Application Links in the Event Mappings

Reconfiguring the REST Grids

Republish the Process Apps