Configuring integration with TADDM 7.2.x

Edit online

You can use the Definitive Media Library application to register software images imported from operational management products (OMPs) into the IBM® Tivoli® Application Dependency Discovery Manager (TADDM) database. As shipped, the release management component is configured to integrate with a TADDM 7.1.x server. You can perform a series of configuration steps to integrate with a TADDM 7.2.x server instead.

About this task

Note that you can disable the integration between the Definitive Media Library application and TADDM. See Disabling TADDM integration for details. If you disable this integration, you do not need to perform the configuration steps in this topic, even if you use launch in context and other product functions that rely on integration with TADDM.
The procedure for configuring release management to integrate with TADDM 7.2.x involves the following steps:
  1. Locating the TADDM 7.2.x API Client JARs and copy them to the administrative workstation
  2. Copying the TADDM 7.2.x API Client JARs to the product installation tree
  3. Removing the TADDM 7.1.x AP Client JARs from the product installation tree
  4. Modifying the RPM deployment XML file
  5. Rebuilding and redeploying the Maximo EAR file
Details for each of these steps are provided in the following sections.