Configure PPM for the integration

This section describes the procedures you need to perform to configure PPM for the integration.

Configure server.conf parameters in PPM

Add (if not present) and specify the parameters related to Universal CMDB integration to the PPMserver.conf configuration file.

Note: For more information about the steps in this procedure, see the Installation and Administration Guide.

To add and specify the parameters in the PPMserver.conf configuration file:

  1. Stop the PPM Server.

  2. Open the <PPM_Home>/server.conf file, add and configure the following parameters:

    All parameter names begin with com.kintana.core.server. but that is not shown in the table.




    URL of the Probe Gateway component of the Discovery and Dependency Mapping (DDM) Probe. The Probe Gateway provides communication (HTTP or HTTPS) between the Probe Manager and the Universal CMDB user for processes such as downloading tasks and returning task results.

    The value for <UCMDB_Host>:<port> is usually the same as for the UCMDB_SERVER_URL parameter.



    Maximum number of CIs a request is allowed to have. Valid values are from 1 to 100. If a value greater than 100 is specified, the PPM Server will not restart and displays an error message. The default is 20.


    Password for Universal CMDB user specified in UCMDB_USER.

    This password must be encrypted as described in Encrypt the password specified as a server.conf parameter.


    URL of the Universal CMDB server:




    where <UCMDB_Host> represents the host machine on which Universal CMDB is running.

    Note: If the Universal CMDB server is configured to support HTTPS, make sure you configure the UCMDB_SSL_KEYSTORE_PATH parameter.


    Do not use.


    Universal CMDB keystore path, used only if the UCMDB_SERVER_URL parameter uses HTTPS.


    Universal CMDB user name, for example, admin.

    This user name must include only single-byte characters.

  3. Run the script to apply your changes. For details, see

  4. Restart the PPM Server.

Encrypt the password specified as a server.conf parameter

The password that you assigned to the UCMDB_PASSWORD parameter must be encrypted.

  1. Navigate to the <PPM_Home>/bin/ucmdb directory.

  2. Run the utility.

  3. Specify the password you want to encrypt.

    The utility encrypts the password and displays the encrypted text.

  4. Copy the text in the Encrypted text section on the screen and paste the text as the value for UCMDB_PASSWORD in the server.conf file, making sure that you do not copy any carriage returns into the file.

Back to top

Configure a request type

The integration requires a request type with the Universal CMDB Impact Analysis field group. The ALM - Request for Change (RFC) request type provided with ALM includes this field group, which is enabled by default.

If necessary, you can add the Universal CMDB Impact Analysis field group to a different request type.

To add a different request type to the Impact Analysis field group:

  1. Log on to PPM.

  2. From the menu bar, select Open > Administration > Open Workbench.

  3. From the shortcut bar, select Demand Mgmt > Request Types.

  4. In the Request Type Workbench, select the request type to which you want to add the Universal CMDB Impact Analysis field group.

  5. Open the request type and its request header type.

  6. Click Field Groups.

  7. In the Field Groups window, scroll down and select the check box to enable the Universal CMDB Impact Analysis field group.

  8. Click OK to add the Universal CMDB Impact Analysis field group to the request header type.

  9. In the Fields tab of the request header type, expand Universal CMDB Impact Analysis in the Prompt column.

  10. Select the CI List field, and click Edit.

  11. On the Attributes tab, select No for the Display Only option and select Yes for the Display option.

  12. Select the Security tab and edit field-level security for the CI List field as needed.

  13. Click OK to save and close the Edit window and click OK to save and close the Request Header Type window.

  14. The request type now has the Universal CMDB Impact Analysis section, including the CI List field, based on the changes you made to the request header type.

  15. Use the Layout tab to reposition the Impacted Configuration Items section on the request type, as needed.

    Note: On the Status Dependencies tab for the CI List field, leave the Required, Reconfirm, and Clear options set to No.

    You can change the Visible and Editable options as needed.

Back to top