Using the MDR Launcher › The MDR Launcher

The MDR Launcher

One of the main purposes for implementing CA CMDB is to aggregate data from multiple data sources (known as MDRs). However, a CI must always include a reference back to its MDR origin.

CA CMDB provides facilities for importing and loading CIs and also for associating the CIs with their origins. In addition, by using the MDR Launcher capability when viewing a CI in the CA CMDB, you can navigate seamlessly back into the system from which the CI originated, as shown in the following diagram.

Using the MDR Launcher, it is possible to implement a “closed loop” change management process such as the following one:

1. Create a change record.
2. Implement the change.
3. Verify the change by checking the MDR source.
4. Update the CMDB to indicate the change has been made.

From a Problem Management process perspective, you can use the MDR Launcher in the following way:

1. Detect a problem.
2. Determine the severity and pervasiveness of the problem by utilizing the CI relationship data to determine what dependent CIs are affected.
3. Determine possible causes of the problem by researching provider CIs.
4. Perform an in-depth analysis if necessary using the highly detailed information available in the MDR, and use the MDR to take corrective action.