428 IBM Tivoli Monitoring: Implementation and Performance Optimization for Large Scale Environments
Once these settings have been defined, the discover process can begin. TADDM
will build a topological view of the defined environment.
12.2.3 Scan IBM Tivoli Monitoring environment using Discovery
Library Adapters
The next step is to scan the known IBM Tivoli Monitoring environment using a
tool known as the IBM Tivoli Monitoring Discovery Library Adapters (DLA). A
DLA is a program that extracts data from a source application (in this scenario,
our IBM Tivoli Monitoring environment), and generates an XML file specifying
details about the managed environment. We then upload the generated XML file
to TADDM for comparison with the discovered environment we generated
The DLA gathers information from the hub monitoring server by querying for all
managed systems and mapping them according to the agent product code and
managed system name format. For agents that use IP, IP.PIPE or IP.SPIPE as
their communication protocol, the DLA can discover the IP address where the
agent is running plus the operating system of the machine hosting the agent
regardless of whether an OS monitoring agent is running on that machine or not.
The DLA also queries the portal server for information regarding logical
groupings within the environment. For this reason, both the portal server and all
monitoring server instances must be
online when running the DLA tool.
Monitoring agents do not have to be online since the information is derived from
the monitoring server and portal server.
The IBM Tivoli Monitoring DLA tool is an executable installed under the portal
server folder. The executable is known by the following names:
򐂰 Windows:
򐂰 UNIX and Linux:
Run the executable from the command line. The tool has the following
arguments available.
KfwTmsDla [-?] [-b] [-d] [-l] [-o orgname] [-s] [-x outputfile]
Note: Ensure that you choose the correct case for any agents you may be
searching for on case-sensitive Linux or UNIX environments. Typically this
should be lower case (for example, kux rather than KUX).
Chapter 12. IBM Change and Configuration Management Database integration 429
-? Display the syntax help information.
-b Opens a browser with which to view the output of the
-d Creates a diagnostic file during the discovery process.
You can use this file for debugging.
-l Indicates to discover logical views.
-o orgname Sets the organization global name.
-s Use HTTPS URL instead of HTTP URL.
-x outputfile Set an alternative name for the XML output file.
We ran it against our environment with the following arguments:
KfwTmsDla -l -o ITSO -x prague.xml
By default, the DLA generates the XML output file in the \tmsdla subdirectory on
the portal server. The name of this file follows the standard Discovery Library file
name format. Example 12-1 shows a sample of the generated XML output.
Example 12-1 Snapshot™ of XML data generated by KfwTmsDwl tool
<cdm:sys.ComputerSystem id="sydney.itsc.austin.ibm.com-ComputerSystem"
<cdm:sys.unix.Unix id="sydney.itsc.austin.ibm.com-Unix"
Tip: On UNIX and Linux, you may need to run the following steps to ensure
the PATH environment variable is set up correctly to run the script:
cd /opt/IBM/ITM/config
. ./cq.config
cd /opt/IBM/ITM/<OS Specific Directory>/cq/bin
. ./pathsetup.sh
where <OS Specific Directory> varies according to the operating system you
are using.

Get IBM Tivoli Monitoring: Implementation and Performance Optimization for Large Scale Environments now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.