IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Administrator's Guide > Use the Tivoli Management Services Discovery Library Adapter
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
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.
Some application agents (such as the DB2 agent) rely on the OS agents to create the elements in the DLA book that describe the computer system and operating systems that the agents are running on. In their DLA templates, the application agents reference the computer system and operating system elements that will be created by the OS agents using a relationship element. For example, a Db2System runsOn a ComputerSystem, where runsOn is the relationship type, Db2System is the source element, and ComputerSystem is the target element.
If an OS agent is not monitoring the same system as an application agent or the OS agent and application agent are connected to different IBM Tivoli Monitoring environments then the source or target of a relationship element might not exist in a DLA book. The source and target of a relationship to a computer system or operating system might also not exist if:
- The Windows OS agent is monitoring a Windows 2000 system. In this case, the OS agent cannot discover the IP address of the Windows 2000 system and, therefore, does not create computer system elements in the DLA book.
- You are using an agentless OS agent to monitor a system that an application agent is also monitoring since agentless OS agents do not provide input to the DLA books.
If either the source or target of a relationship do not exist in the DLA book, the book will not load successfully into Tivoli Application Dependency Discovery Manager (TADDM) or Tivoli Business Service Manager (TBSM). Therefore, the DLA removes a relationship from an DLA book if the source or target of a relationship do not exist in the book. This allows the DLA books to load successfully. However, if a relationship is removed, the DLA book will not contain the information to map the affected resource (such as a database system) to a computer system or operating system in TADDM or TBSM.
The DLA creates two XML files each time the tmsdla command is run:
- A book with the .xml extension
- A book with the .xml.original extension
The file with the .xml.original extension contains the contents of the DLA book before any relationships are removed. Removed relationships are written in tmsdla.log.
If you want your resources to be mapped to computer systems and operating systems in the DLA books that are loaded into TADDM and TBSM, install an OS agent on the systems that are being monitored by your application agents.
Parent topic:
Use the Tivoli Management Services Discovery Library Adapter