Hybrid Data Acquisition Approach

In many cases, dependency data is not maintained by an MDR. For example, a management application of a messaging solution such as IBM MQ might include information about any MQ-Server in the organization and the queues it realizes. However, the MDR of the MQ management application does not include information about business applications that use any of the MQ Servers. To discover dependency data of a business application with MQ, you need to write a specific discovery pattern that extracts this configuration data from each specific application. A Federation or Replication Adapter should be written to federate or populate the detailed configuration data from an MDR. In addition, a Discovery Adapter should be written to access the managed entities directly and extract dependency data.

If the MDR does not include the required level of details to support the necessary ITIL process, you can select one of the following approaches:

• Access both the MDR and the managed entities. First, import the initial, non-detailed data from the MDR and then access managed entities directly to import more detailed configuration data.
• Do not access the MDR at all. Import all the data from the managed entities.