Configuring Tivoli Application Dependency Discovery Manager Observer jobs
IBM Tivoli Application Dependency Discovery Manager Observer jobs retrieve network topology data, including discovered applications, their components, configurations and dependencies, from the Tivoli Application Dependency Discovery Manager database server (running either an IBM Db2 or an Oracle database), and use this data to create topology views.
Before you begin
Important: The Tivoli Application Dependency Discovery Manager Observer supports the on-premises Tivoli Application Dependency Discovery Manager version.
To connect to a Tivoli Application Dependency Discovery Manager Oracle database, you must place the Oracle JDBC Driver into the $ASM_HOME/lib folder, and then restart the observer for it to take effect. You can download the driver from the Oracle website, or copy it from the Oracle server (not the Oracle client) from the following location: ../app/oracle/product/Oracle_version/dbhome/jdbc/lib/ojdbc6.jar
Ensure you have the Tivoli Application Dependency Discovery Manager Rest API login access details in hand, such as the Tivoli Application Dependency Discovery Manager API URL, username and password.
Enabling access to the URL routes
To access the URL routes for the topology Swagger documentation, see the Enabling access to URL routes topic.
About this task
The Tivoli Application Dependency Discovery Manager Observer is built on the Observer framework:
- A computer system can be a host, server, router, or switch
- A computer system contains CPU, L2Interface, and storage
- Operating system, application server and service run on a computer system
- A computer system can connect to another computer system
- A SAPSystem contains collection
- An application server can be a member of a collection
Mapping Tivoli Application Dependency Discovery Manager model objects to topology entity types
| Tivoli Application Dependency Discovery Manager model object | Entity types |
|---|---|
| AppServer | application |
| ComputerSystem | host, server, router, switch |
| CPU | cpu |
| L2Interface | networkinterface |
| IpInterface | networkinterface |
| IpAddress | ipaddress |
| OperatingSystem | os |
| Service | service |
| StorageExtent | storage |
| Function | service |
| SAPSystem | application |
| Collection | group |
Tivoli Application Dependency Discovery Manager Observer jobs retrieve topology data using the Tivoli Application Dependency Discovery Manager REST API, and the observer loads and updates the resources and their relationships within the topology service.
You define and start the following jobs.
Load job
By default, Load jobs are one-off, transient jobs that do a full upload of all requested topology data as soon as they are triggered.
You can also run these jobs (again) from the Observer UI, or schedule them to run at set times when configuring them.
Procedure
Define or edit the following parameters, then click Run job to save and run the job.
Encryption requirement: See the Configuring observer jobs security topic for more information.
| Parameter | Action | Details |
|---|---|---|
| Unique ID | Enter a unique name for the job | Required |
| TADDM API URL | Specify the Tivoli Application Dependency Discovery Manager endpoint to connect to | Required. |
| TADDM username | Specify the Tivoli Application Dependency Discovery Manager username | Required |
| TADDM password | Specify the password for the Tivoli Application Dependency Discovery Manager user | Required |
| TADDM objects to observe | Select one or more options from the drop-down list | Optional. If none are selected, all supported model objects are retrieved. |
| Generate debug support file | Set this parameter to 'True' in order to capture the output of the next scheduled job run as a file. This file will be stored with an observer's log files and can be used to debug observer issues, for example at the request of your designated Support team, or while using a test environment. For one-off jobs (that is, Load jobs), this parameter reverts to 'False' after the next completed run. To examine the output produced, you can load the generated debug file using the File Observer. | Optional |
| Job schedule | Specify when the job runs | Optional. Load jobs only. |
| Observer job description | Enter additional information to describe the job | Optional |