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 a IBM DB2 or an Oracle database), and
use this data to create topologies within the Agile Service Manager topology service.
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 them 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.
The TADDM Observer is installed as part of the core installation procedure.
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
Table 1. Mapping TADDM model objects
to Agile Service Manager entity types
| TADDM model object |
Agile Service Manager 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. The observer loads and
updates the resources and their relationships within the Netcool Agile Service Manager core topology
service.
You define and start the following jobs.
- Load job
- By default, these jobs are one-off, transient jobs that carry out
a full upload of all requested topology data when they are triggered.
- You can also run these jobs (again) manually from the Observer
UI, or schedule them to run at set times when you configure them.
Procedure
-
On the Observer jobs page, perform one of the following actions:
- To edit an existing job
- Open the List of options overflow menu next to the job and click
View & edit.
- To create a new job
- Click Add a new job + and select the TADDM Observer tile.
-
Enter or edit the following parameters, then click Save to save your job
and begin retrieving information:
Table 2. TADDM Observer load
job parameters
| Parameter |
Action |
Details |
| Unique ID |
Enter a unique name for the job |
Required |
| TADDM API URL |
Specify the TADDM endpoint to connect to. |
Required. |
| TADDM username |
Specify the TADDM user name. |
Required |
| TADDM password |
Specify the password for the TADDM user. |
Required. Use plain text. |
| 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. |
| 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
parameters, such as matchTokens.
|
Optional. Tip: You can define access scope for locations, project names,
namespaces, and so on.
|
| Generate debug support file |
Set the optional Generate debug support file
parameter to True to capture the output of the next scheduled job run as a file.
This file is 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. The file is saved to the following locations:
- On-premises
- $ASM_HOME/logs/<obs>-observer/
- On OpenShift Container Platform
- /var/log/itsm/<obs>-observer
|
Optional |
| Observer job description |
Enter additional information to describe the job. |
Optional |
| Job schedule |
Specify when the job should run, and whether it should run at regular intervals.
By default the job runs immediately, and only once.
Optionally you can specify a future date and time for the job to run, and
then set it to run at regular intervals after that.
|
Optional. Transient (one-off) jobs only.
If you set a job schedule, the run intervals must be at least 90 seconds apart. If you set them
at less than 15 minutes, a warning is displayed, as the frequency can impact system performance.
|
