Integrating TADDM with IBM Tivoli Monitoring (old method)

Depending on the specific tasks that you must do in your IT environment, you can use the integration capabilities that are available between IBM® Tivoli® Application Dependency Discovery Manager (TADDM) and IBM Tivoli Monitoring. You can integrate TADDM with IBM Tivoli Monitoring by using IBM Tivoli Monitoring Scope sensor.

New integration method

Important: Starting with the TADDM version 7.3.0, it is advised to integrate with IBM Tivoli Monitoring 6.3 using OSLC Automation. The old method of integration with the use of IBM Tivoli Monitoring Scope sensor is deprecated and will be removed from future releases.

Learn more about TADDM integration with IBM Tivoli Monitoring by using OSLC Automation at Integrating TADDM with IBM Tivoli Monitoring via OSLC Automation and about sensors that support discovery using OSLC Automation at Sensors that support discovery using OSLC Automation.

The old integration method

All of the following sections apply to the old method of integration. You can still use it, but remember that this method is deprecated and will be removed from future releases.

Table 1. correlates some tasks that you might need to do with the integration capabilities that you should use, and the remaining sections provide an overview of these integration capabilities.

Table 1. User tasks with corresponding integration capabilities to use
Task	Integration capability to use
Gain insight into availability by viewing the operating system settings, application settings, and change history of systems that are monitored by IBM Tivoli Monitoring.	Discovery using IBM Tivoli Monitoring Launch in context
Ensure that operating systems that are discovered by TADDM are monitored for availability.	Discovery using IBM Tivoli Monitoring Monitoring Coverage reports
View the availability and performance of systems that are discovered by TADDM.	IBM Tivoli Monitoring DLA Monitoring Coverage reports
Monitor a business application for configuration changes.	Discovery using IBM Tivoli Monitoring Change events Launch in context

Discovery using IBM Tivoli Monitoring

TADDM can perform Level 1, Level 2, and some Level 3 discoveries using an IBM Tivoli Monitoring 6.2.1 or later infrastructure. TADDM discovers configuration items in the IBM Tivoli Monitoring environment by using only the credentials for your Tivoli Enterprise Portal Server rather than the credentials for each computer that the portal server monitors.

TADDM leverages the Tivoli Monitoring infrastructure in the following two ways:

TADDM obtains the list of Tivoli Monitoring endpoints from the Tivoli Enterprise Portal Server both to create basic Level 1 discovery information and to create scopes for deeper Level 2 and 3 discovery.
TADDM uses the Tivoli Monitoring infrastructure both to run CLI commands on target systems for the sensors in Level 2 and 3 discovery and to capture the output of those commands

This capability provides the following benefits:

Rapid deployment of TADDM in existing Tivoli Monitoring environments
No need for TADDM anchor and gateway servers
No need to define scope sets that contain computers to scan. Only a scope with a single entry for the Tivoli Enterprise Portal Server is required.
No need to define an access list (operating system credentials) for discovery targets
Only a single access list entry for the Tivoli Enterprise Portal Server GUI logon is required.

Table 2. Topics that contain more information about discovery using IBM Tivoli Monitoring
Information	Location of information
Configuring for discovery using IBM Tivoli Monitoring	Configuring for discovery using IBM Tivoli Monitoring (old method)
TADDM server properties that apply to discovery using IBM Tivoli Monitoring	Properties for discovery using IBM Tivoli Monitoring (old method)
Sensors that support discovery using IBM Tivoli Monitoring IBM Tivoli Monitoring Scope sensor, including information about configuring the sensor and about troubleshooting any known problems that might occur when deploying or using the sensor	Sensor reference

IBM Tivoli Monitoring DLA

The IBM Tivoli Monitoring discovery library adapter (DLA) extracts configuration data from Tivoli Monitoring about the computer systems and databases that Tivoli Monitoring monitors. The output of the DLA is a formatted XML file that contains these components and their relationships. The output of the DLA also includes data that represents Tivoli Monitoring agents and data that is used for launching availability views from TADDM. For detailed information about loading the DLA-exported data into TADDM, see The bulk load program.

To run DLA, complete the following steps:

Generate DLA on ITM as specified in the Using the Tivoli Management Services Discovery Library Adapter topic at http://www-01.ibm.com/support/knowledgecenter/SSTFXA_6.2.2.1/com.ibm.itm.doc_6.2.2fp1/discoverylibraryadapter_tms.htm?lang=en.
Copy the DLA output file to the TADDM host.
Use the bulk load program to load DLA from ITM to TADDM. Use the following command:
```
$COLLATION_HOME/bin/loadidml.sh -u user -p password -f path_to _DLA
```

When you install new Tivoli Monitoring agents, they can provide additional support to the Tivoli Monitoring DLA. The agents provide information to populate the monitoring coverage reports, only the monitoring coverage for operating systems report does not require a DLA.

When you install an agent, you must enable application support for those agents to ensure that the agent participates in the output generated by the DLA. Not all agents support the Tivoli Monitoring DLA.

For information about configuring application support for non-standard agents, see the appropriate documentation. To verify that an agent supports the Tivoli Monitoring DLA, see the documentation for the IBM Tivoli Composite Application Manager agent.

Monitoring Coverage reports

The Monitoring Coverage reports show details about various components in your environment. You can generate a report for operating systems, databases, Microsoft applications, VMware servers, and System p components in your environment. These components are monitored by IBM Tivoli Monitoring 6.1 or later agents.

For more information about Monitoring Coverage reports, see TADDM User's Guide.

Change events

You can configure TADDM to notify IBM Tivoli Monitoring when a change to a discovered resource is detected.

Table 3. Topics that contain more information about change events
Information	Location of information
Configuring TADDM to send change events Configuring an IBM Tivoli Monitoring data provider Configuring change events for a business system	Sending change events to external systems

Launch in context

With launch in context, you can view TADDM data within the Tivoli Enterprise Portal views of IBM Tivoli Monitoring.

By configuring topology views to show in the Tivoli Enterprise Portal, you can view physical infrastructure, application infrastructure, and business system topologies within Tivoli Enterprise Portal availability views.

Table 4. Topics that contain more information about launch in context
Information	Location of information
URLs that are required for display of topology views	Configuring for launch in context
Instructions for configuring launch in context for viewing the operating system settings, application settings, and change history for incoming change events	Creating detail links in configuration change event reports in IBM Tivoli Monitoring