CA Service Management - 17.2

17.3 17.2 17.1 14.1
English

Step 2 - Perform Setup Tasks for CMDB

As a CMDB administrator, on the CMDB computer, log on to CMDB. Access the CMDB Administration tab, and perform the following tasks.
casm172
As a CMDB administrator, on the CMDB computer, log on to CMDB. Access the CMDB Administration tab, and perform the following tasks.
  1. Using the Web Services Policy option, create the Web Services Access policy.
    1. Assign a name. The suggested name and code are USM_CMDB_Policy, but you can use any name that meets your needs.
    2. Assign a proxy user to this policy.
      This proxy user
      must
      have administrative access to CMDB.
    3. Verify that the Allow Impersonate property of CMDB is set to Yes.
    CMDB checks the access type of the CA Service Catalog user to be impersonated against the access type of the policy proxy user. If the access level of the CA Service Catalog user is less than or equal to the grant level of the proxy user‘s access type, CMDB replaces the CA Service Catalog user with the proxy user. For more information, see your CMDB documentation.
  2. Generate the policy key file for the Web Services Access policy that you created. To generate the key file, use the pdm_pki tool.
    The suggested name is USM_CMDB_Policy.p12, but you can use any name that meets your needs.
    Verify that the HasKey property is set to Yes in the newly created Web Services access policy. The system typically configures this setting automatically when you generate the policy key file.
    Copy the policy key file to the CA Service Catalog server and save it in the USM_HOME directory.
    If you are using application clustering, copy the policy key file to the USM_HOME directory of
    every
    Catalog Component cluster node.
  3. Verify that the Business Service class of the Enterprise Service family exists. This class is required for CA Service Catalog users to create a configuration item in CMDB. If this class does not exist, create it manually or run the CMDB installation again to load default data.