Integration → Plug-ins → Integrating with Dimensions CM → Configuring Dimensions CM Processes in Deployment Automation → Configuring the Dimensions CM Application

Configuring the Dimensions CM Application

An application process is used to run the component processes you need. Most of the properties that are needed for the component processes should be set at the application level, because many properties are used by more than one component process.

When the application process is initiated through Release Manager deployment tasks, a small set of values are passed as part of the request. Any properties with no values passed will use the values set in the application. If no values are set, the default values will be used.

Tip: For the quickest implementation, import the sample environment and application and modify the properties to suit your needs.

To configure the application:

  1. Create an application that will contain your properties and component processes or select an existing one. For example, DimCM Application.
  2. If you imported the sample application, edit the application and change the application name and description to match your implementation's values.
  3. Add properties to your application that are common to all component processes, or modify the existing imported values to match your system information. For example, the connection information property values are as follows:
    • DIMCM_DBCONNECTION: value <your DB connection name>
    • DIMCM_DBNAME value <your DB name>
    • DIMCM_SERVER value <your server name>
    • DIMCM_SERVICE_USER value <your service user name>
    • DIMCM_SERVICE_PASSWORD value <your service user password>
  4. Add the following processes to your application if they have not already been imported.
    • Deploy Baseline
    • Get Baselines
    • Get Deployment Areas
    • Get Products
    • Get Projects
    • Get Projects and Streams
    • Get Stages
    • Get Streams
    • Promote Baseline
  5. Add the properties to the application processes that the component processes will inherit, or change them in the imported application. The properties for which values will be passed to and from Release Manager have an RM$ at the beginning of the value, as shown in the following properties for Deploy Baseline.
    • name DIMCM_PRODUCT, label Product, value RM${applicationProcess:Get Products;displaycols:product}
    • name DIMCM_PROJECT_NAME, label Project Name, value RM${applicationProcess:Get Projects And Streams;properties:{[name:DIMCM_PRODUCT,value: DIMCM_PRODUCT]};displaycols:project_stream}
    • name DIMCM_BASELINE_NAME, label Baseline Name, value RM${applicationProcess:Get Baselines;properties:{[name:DIMCM_PRODUCT,value: DIMCM_PRODUCT]};displaycols:baseline}
    • name DIMCM_STAGE_NAME, label Stage Name, value RM${applicationProcess:Get Stages;displaycols:stage}
    • name DIMCM_DEPLOYMENT_AREAS, label Deployment Areas, value RM${applicationProcess:Get Deployment Areas;properties:{[name:DIMCM_PRODUCT,value: DIMCM_PRODUCT],[name:DIMCM_PROJECT_FILTER,value: DIMCM_PROJECT_NAME],[name:DIMCM_STAGE_NAME,value: DIMCM_STAGE_NAME]};displaycols:deployment_area}
    • name DIMCM_REASONS, label Reasons, value none

Related Topics

Designing Processes

Importing the Dimensions CM Sample Environment

Importing the Sample Dimensions CM Application

Copyright © 2011–2015 Serena Software, Inc. All rights reserved.