Logging this query on behalf of a customer.
They would like to know "How to use GRLoader to create and maintain two MDRs against the same Configuration Item?"
Does anyone have some pointers?
This is what works for a single MDR and Configuration Item:
The challenge now is to add a second MDR against the same Configuration Item using GRLoader.
The documentation appears to indicate it is possible. Here is the current documentation.
MDR Classes and MDR Names
An IT enterprise can include many MDRs. Each MDR has an identifier that is known as an MDR name (mdr_name). It is common for an MDR to use the host server name as the mdr_name. The server name is used to allow multiple MDRs to reside on the same host server. Therefore, an MDR class (mdr_class) is appended to the mdr_name to identify each MDR uniquely.
CA Configuration Automation is an enterprise discovery tool that integrates tightly with CMDB Each CA Configuration Automation MDR defined to the CMDB must have an mdr_class of Cohesion. For more information about CA Configuration Automation, see the CA Configuration Automation online help. For CA Configuration Automation-CMDB integration, see the CA Configuration Automation Implementation documentation.
Every MDR has a unique way of identifying the CIs that it manages. Those identifiers are seldom synchronized across MDRs. For example, when referencing a specific Contact CI, different MDRs can use different identifiers. A national identity number, telephone number, license number, or Employee ID can identify the same person. The process of associating these disparate identifiers with the same unique identifier (UUID) maintained in the MDB is named mapping. Mapping occurs automatically when data is imported using GRLoader when the CI contains the <mdr_name> <mdr_class> and <federated_asset_id> tags. Mapping can also be accomplished manually through the Administration functions in the user interface. A CI that has no mappings that are associated with it is named unfederated. Every CI is automatically mapped to global MDRs using the UUID as the federated_asset_id.
I interpreted this to mean that just two sequential data loads could be done.
I don't have the test load file yet, but the reported result was:
Running GRLoader with two entries for the same CI, one with the first MDR and one with the second MDR results in only the second MDR being set up, the first one is added and then replaced.
Any suggestions welcome.