Configuring TADDM Observer jobs
IBM Tivoli Application Dependency Discovery Manager (TADDM) Observer jobs retrieve network topology data, including discovered applications, their components, configurations and dependencies, from the TADDM database server (running either an IBM Db2 or an Oracle database), and use this data to create topology views.
Before you begin
Important: The TADDM Observer supports the on-premise TADDM version.
To connect to a TADDM 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 TADDM Rest API login access details in hand, such as the TADDM 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 TADDM 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 TADDM model objects to topology entity types
| TADDM 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 |
TADDM Observer jobs retrieve topology data using the TADDM 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 password | Specify the password for the TADDM user | Required |
| TADDM API URL | Specify the TADDM endpoint to connect to | Required. |
| TADDM username | Specify the TADDM username | 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. |
| TADDM certificate | Specify the certificate file name. | Optional |
| Certificate validation | Choose whether SSL validation is on or off. Turning SSL validation off will use HTTPS without host verification. |
Optional |
| Connection and read timeout (ms) | Enter the time at which the connection and read actions time out | Optional. Must be a value greater than 0 (zero), and the default is 5000 (5 seconds). |
| Trust all certificates verification | Set to true to allow connection to target environment without verification. | Optional. The default is 'false'. |
| Access scope | Enter text to provide a scope for the resources. Access scope can help map alerts to resources when resources in different scopes share the same parameters, such as matchTokens. | Optional. Tip: You can define access scope for locations, project names, namespaces, etc. |
| 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 |
| Observer job description | Enter additional information to describe the job | Optional |
| Job schedule | Specify when the job runs | Optional. Load jobs only. |