About MDR

This article contains the following topics:
This article contains the following topics:
The Configuration Management Database Federation (CMDBf) is a working group that is composed of representatives from CA, IBM, HP, Microsoft, and other companies. The CMDBf defines a Management Data Repository (MDR) as anything that collects information about configuration items (CIs).
To create the relationship between an MDR and its CIs when implementing MDR Launcher, complete the following tasks:
  1. Define the MDR.
  2. Define the CIs that reference that MDR.
    You cannot have a CI that references a non-existent MDR. You can define a CI without defining an MDR association. You can add the MDR information during an update or can edit to take advantage of the MDR Launcher capability.
Multiple MDRs can discover the same CI. After the CI is discovered, each MDR attempts to manage that CI, and an MDR can do the following actions:
  • Discover detailed attributes about the CI.
  • Attempt to modify the CI state.
Example: A CI Discovered by Multiple MDRs
Both Network Management software and an Asset Management software package discover a CI.
  • The network management software maintains information about network configuration and network topology.
  • The asset management software contains information regarding cost, depreciation, licensing, and maintenance contracts for that particular CI.
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
. 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
How does an MDR Complement CA SDM?
An MDR typically contains more detailed CI information than CMDB. However, a single MDR is not typically aware of the existence of other MDRs. It does not focus on the relationships that a particular CI can have with other CIs, especially if they are contained in other MDRs. CMDB manages this type of environment well, because it focuses on managing CIs regardless of their MDR source.
CMDB is not intended to store all attributes for all CIs. CMDB is used to consolidate the most important attributes that must be managed centrally. Attributes that are under the control of change management are excellent candidates for inclusion in the CMDB. Attributes that CMDB does not manage can be accessed by using the MDR Launch capability. In addition, CMDB provides the CMDBf Viewer. CMDBf Viewer allows side by side comparison of CI attributes across multiple CMDBs and MDRs.
MDR Launcher
The MDR Launcher lets you view data from almost any MDR by using a web page, without any coding. MDR Launcher lets anyone viewing a CI to obtain more details about the CI, and to gain control over it (if the MDR supports such control).
Some uses of the MDR Launcher include the following ones:
  • From the hardware.server detail page, launch CA Configuration Automation to verify a change.
  • From an Air Conditioning CI detail, launch to a vendor web page for diagnostic information and incident reporting.
  • From a Contract CI, launch a contracts management system to learn contract details.
  • From an SLA CI, launch CA Service to review Service Level Agreements before modifying.
  • From a Server CI, launch CA Remote Control to take over the server to diagnose and correct a problem.
Define a URL to Launch an MDR
CMDB uses a URL to start a web page session with the source MDR to operate the MDR Launcher. You define the URL that CMDB uses.
Follow these steps:
  1. Click the Administration tab.
  2. In the left pane, open the 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 that the Hostname web server uses.
    • Path
      Specifies the path to the web page, including the page itself.
      Specifies  any parameters that are used to identify the desired CI to the MDR. 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 that is shared between CMDB and the MDR. For CA Cohesion MDRs, this value must match the value that is 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.
       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.
  7. Save the definition. 
The URL is defined. In addition, the URL can contain the substitution variables to further qualify the CI to the MDR. For more information, see the Using the MDR Launcher topic.
Set Up a CA APM MDR Provider
You can set up an MDR to be the CA APM provider.
Follow these steps:
  1. On the Administration tab, click CMDB, MDR Management, MDR List.
  2. Click Create New to specify the CA APM MDR.
    The MDR Provider definition appears.
  3. Enter the following required MDR provider information:
    • Button Name -- Specify APM or any other valid button name. We recommend using a Button Name of APM.
    • MDR Name -- Specify APM for CA Asset Portfolio Management r11.3.4 or ITAM for CA APM r12.6
    • MDR Class -- Specify GLOBAL.
    • Hostname -- Specifies the CA APM server name by using the network address or the DNS name of the CA APM web server.
    • URL for Launch in Context -- Specifies http://{hostname}:{port}/{path}?{parameters} and must not be changed.
    The MDR provider form automatically populates the path and parameter values with the required CA APM launch in context information.
  4. Click Save.
    The CA APM MDR provider is set up. For more information about the MDR launcher, see the MDR Launcher topic. 
Launch in Context from CMDB to CA APM
The CMDB MDR Launcher facility supports launch in context to CA APM when the tools share the same MDB. The CMDB UI provides a launch in context button on the Attributes tab in the CI detail form. The button appears when the user creates a special CA APM MDR provider definition.
The CA APM MDR definition has all the capabilities of a traditional MDR. The CMDB Versioning feature also supports launch in context directly from an attribute log entry that is associated with each CA APM change.
Unlike other MDRs, the CA APM MDR is automatically associated with each CI or Asset. The MDR class of GLOBAL and MDR name of APM are used to identify the CA Asset Portfolio Management r11.3.4 MDR. The MDR class of GLOBAL and MDR name of ITAM are used to identify the CA APM r12.6 MDR. Use of the CA APM MDR is fully compatible with other MDRs, even for the same CI.