Administering MDRs › CA Cohesion ACM MDRs › CI to MDR Mapping

CI to MDR Mapping

Because each MDR uses a federated_asset_id to identify a CI, one CI can be related to multiple MDRs. A federated_asset_id does not have to be unique across MDRs, but a federated_asset_id must be unique within an MDR. Each MDR must have a unique MDR class and MDR name.

Important: Whenever a CI or an MDR provider is made Inactive, all Federated CI Mappings associated with the CI or the MDR provider are also made Inactive.

After you create an MDR Data Provider definition, do the following:

1. Create a CI in the CMDB that references an MDR.
2. Verify that the MDR definition works.

   Because you can only launch from within the context of a CI, it is not possible to test directly from the MDR definition, which has no CI context.

You can view the Federated CI Mapping List in the Administration tab, in the Federated CI Mapping node.

To view the CI in a particular MDR context, click an MDR Launch button.

The target MDR is launched in the context of the CI that was opened.

Example: CI Mapping

1. Click the Administration tab.
2. Navigate to MDR Management, Federated CI Mapping.

   The Federated CI Mapping List appears.

3. Enter server1 in CI Name field.

   The following columns show the values:

   Federated Asset ID

   1000234

   1000235

   CI Name

   server1

   server1

   MDR Provider

   Cohesion1

   Cohesion2

   Active

   Active

   Active

   The Cohesion1 MDR Provider knows of the existence of server1, and the Cohesion2 MDR Provider also knows of the existence of server1. The example shows that they each have independently assigned the server a unique ID.

4. Click the CI Name server1.

   The server1 Configuration Item Detail page appears that includes launch buttons would be named Cohesion1 and Cohesion2.

5. Click either MDR Provider launch button.

   Additional details about the CI appear.