Working with the discovery library adapter

System Automation Application Manager provides a Discovery Library Adapter (DLA) to export the currently active System Automation Application Manager resource topology to an Identity Markup Language (IdML) discovery book.

The resulting IdML book can be loaded into IBM® Tivoli® Application Dependency Discovery Manager (TADDM). The loaded IdML book replaces any previous configuration items that are related to this System Automation Application Manager instance. For more information about TADDM, see http://www.ibm.com/software/tivoli/products/taddm.

For information about the configuration of the DLA, refer to Discovery Library Adapter tab.

You use the command eezdla to create IdML books for System Automation Application Manager. Proceed as follow:
  1. Log on to the system on which the automation manager is running.
    Note: While the end-to-end manager is kept highly available, the end-to-end manager moves from one system to another.
  2. Enter the command eezdla
  3. When the command is completed, check its return code using the command echo $?.

    The following table lists the return codes that are returned by the command eezdla.

    Table 1. eezdla return codes
    Code Description
    0 an IdML book was created successfully.
    1 the usage statement was displayed as the eezdla script was started with a parameter; no IdML book was created.
    2 an error occurred; no IdML book was created.
If the return code is 2, check the message log of the end-to-end automation engine for indications why the DLA failed. You can either use the "View log" function for the end-to-end domain in the operations console, or open the message log file directly (msgEngine.log or msgFlatEngine.log). Log files are stored in the subdirectory eez/logs of the Tivoli Common Directory.

Alternatively, set up a scheduling tool to regularly start the eezdla script.

The resulting IdML book is stored at the location that is configured on the Discovery Library Adapter tab in the end-to-end configuration tool.

Following the guidelines for naming IdML books, the names of IdML books created by System Automation Application Manager start with the application code "EEZ", followed by the host name of the system on which the automation manager is installed and an Coordinated Universal Time timestamp. For example: 
EEZ3210.e2esrv1.friendly.com.2010-02-15T14.57.47.093Z.refresh.xml