Use the Tivoli Management Services Discovery Library Adapter

IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Administrator's Guide
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2

Use the Tivoli Management Services Discovery Library Adapter

Use the Tivoli Management Services Discovery Library Adapter (TMS DLA) program for scanning your monitored environment to identify the managed systems. You can then feed this information (an XML output file) into the Change and Configuration Management Database (CCMDB), Tivoli Application Dependency Discovery Manager (TADDM), or Tivoli Business Service Manager (TBSM). The TMS DLA identifies all distributed and z/OS managed systems registered to the Tivoli Management Services.
When the tmsdla script is launched, the TMS DLA gathers information by querying the hub monitoring server for all managed systems and mapping them to Common Data Model resources based on the agent product code and managed system name format. The queries specified in the XML input file provided by each product are run and the results saved to a single output file.
See the agent-specific user guide’s to determine if the agent supplies an input XML file for the TMS DLA and possible mapping information between the agent’s monitored resources and Common Data Model resources.
The monitoring servers and the Tivoli Enterprise Portal Server must be running for these queries. Also, any managed systems that are not online will be ignored.

Run the following TMS DLA script from the command line on the computer where the portal server is installed:

Procedure
To make a create-type IDML book, enter the following command:
     install_dir\CNPS\tmsdla.bat
Alternatively, to make a refresh-type IDML book, enter the following command. After you import into TADDM, any systems that are offline (such as for maintenance operations) are removed from TADDM. The same is true for Tivoli Business Service Manager (TBSM).
     install_dir\CNPS\tmsdla.bat -r
To make a create-type IDML book, enter the following command:
     install_dir/bin/itmcmd execute cq "tmsdla.sh"
Alternatively, to make a refresh-type IDML book, enter the following command. After you import into TADDM, any systems that are offline (such as for maintenance operations) are removed from TADDM. The same is true for TBSM.
     install_dir/bin/itmcmd execute cq "tmsdla.sh -r"
Results
The TMS DLA generates the XML output file to the same directory on the portal server. The name of this file follows the standard Discovery Library file name format. To use this information in CCMDB, TADDM, or TBSM you must transfer the XML file to the Discovery Library File Store and then use the Discovery Library Bulk Loader.
The TMS DLA also creates an output file with the .xml.original extension which contains the TMS DLA output before any relationships are removed. Removed relationships are written to tmsdla.log. See OS agent dependency for examples of scenarios where relationships might be removed from the TMS DLA XML output file.
Usage
Use the following usage notes for your reference:
tmsdla [ [-? | -h] [-d directory] [-f outputFilename] [-l] [-m listOfManagedSystems]
         [-o] [-p portNumber] [-r] [-s] [-t threadCount] [-w waitTime] ]
where:
-? | -h

Displays the syntax help information.

-d

Specify the template directory location.

-f

Specify the resulting output file name.

-l

Discovers logical views.

-m

Specify the list of managed systems.
The list is double quote delimited and follows this syntax:
"os_msys1, os_apptype1, [msys1, apptype1] ~ [os_msys2, os_apptype2, 
[msys2, apptype2]] ~ .. ~ [os_msysN, os_apptypeN, [msysN, apptypeN]]"
-o

Force processing of offline managed systems.

-p

Specify the portal server's port number if it is not the default value of 1920. The port number is included in the output book and used by TADDM or TBSM to generate the URL to launch to the Tivoli Enterprise Portal.

-r

Generate a refresh-type output XML file. After you import a refresh-type output file into TADDM, the objects for any managed systems that are offline, such as for maintenance operations, and their monitored resources are removed from the TADDM database. The same is true when you import a refresh-type output file into TBSM or CCMDB. If you do not specify this option, a create-type output XML file is generated that only contains online managed systems and the resources that they are monitoring. When you import a create-type output XML file into TADDM, TBSM, or CCMDB, managed systems and monitored resources are added or updated but no deletions occur.

-s

Suppress generation of the .original file from cleanup process.

-t

Specify the number of threads to use.

-w

Specify the number of seconds to wait for query to be serviced by agent before timing out. Use this option if monitoring agents might not be able to service queries in a reasonable time due to a heavy load on the queried system. Default value: 120 seconds.

Minimum value: 50 seconds. Values lower than 50 are ignored and the default value is used.

Maximum value: 600 seconds.

Note: No return codes are provided on the completion of the book to alert you if there was a timeout or missing agent data. To determine if you need to set a higher value than the default, analyze the book to ensure that all agents have responded.
OS agent dependency
The Tivoli Management Services Discovery Library Adapter (TMS DLA) requires operating system (OS) agents to monitor the same systems as application agents that provide DLA templates.

Private network address filtering
In environments where private network addresses are not duplicated, you can change this behavior so that the Tivoli Management Services Discovery Library Adapter (TMS DLA) populates these computer systems.

Related reference:

Tivoli Change and Configuration Management Database
Problems with the Tivoli Monitoring DLA
Tivoli Monitoring Command Reference

+
Search Tips | Advanced Search