Previous Topic: MDR Launcher

Next Topic: Set Up a CA APM MDR Provider

Define a URL to Launch an MDR

CA CMDB uses a URL to start a web page session with the source MDR to operate the MDR Launcher. You define the URL that CA CMDB uses.

To define an URL for an MDR

  1. Click the Administration tab.
  2. In the left pane, open the CA CMDB, MDR Management tree.
  3. Click MDR List.

    The Management Data Repository (MDR) List page appears.

  4. Click an existing MDR (or create and save a new one).

    The MDR Provider Definition page appears.

  5. Click Edit.

    The Update MDR Definition page appears.

  6. Complete the following parameters:
    Hostname

    Specifies the Network address or DNS name of the web server that serves up web pages for the MDR.

    Port

    Specifies the port number used by the Hostname web server.

    Path

    Specifies the path to the web page, including the page itself.

    Parameters

    Specifies the any parameters used to identify the desired CI to the MDR. CA CMDB posts this information to the MDR.

    Userid

    Specifies the userid, if a common userid is allowed access to the MDR.

    Shared Secret

    Specifies information shared between CA CMDB and the MDR. For CA Cohesion MDRs, the value specified here must match the value specified in the CA Cohesion properties file, for the com.cendura.security.oneclickauth.secret value.

    CMDBf Namespace

    Specifies the federated_asset_id that is passed to the query as a local ID. For CA CMDB, the value is http://cmdb.ca.com/r1.

    CMDBf Timeout

    (Optional) Specifies time limit for CMDBf endpoint query. Default is ten (10) seconds.

    CMDBf Endpoint

    Specifies the Query Service endpoint for the MDR. Required for CMDBf Viewer and retrieving updated MDR data. If you use CA CMDB as an MDR provider, the value is http://cmdb_hostname:cmdb_port/axis/services/QueryPort.

    Save the definition.

    The URL is defined.

Note: In addition, the URL can contain the substitution variables to further qualify the CI to the MDR. For more information, see the Implementation Guide.