Tivoli Application Dependency Discovery Manager policies

You can create policies that interact with your Tivoli® Application Dependency Discovery Manager (TADDM) environment. These policies can forward updates such as, new, changed, or destroyed resources to your TADDM server.

Two types of policies are associated with TADDM:

Initialization

Initialization policies establish communication with a TADDM server and only contain the Configure Tivoli Application Dependency Discovery Manager Integration activity. For every TADDM server you want to update, you must have a matching Configure Tivoli Application Dependency Discovery Manager Integration activity.

Cloud Pak System Software Monitoring Server provides the TADDM_Initialization policy as a template. This policy includes one Configure Tivoli Application Dependency Discovery Manager Integration activity.

To set up your TADDM integration, complete the following steps:

Click Workflow Editor.
Select the TADDM_Initialization policy, and click Copy Policy. Give the new policy a meaningful name, such as TADDM_Init_Austin3.
In the workflow for your new policy, double-click the Configure Tivoli Application Dependency Discovery Manager Integration activity and enter your specific server information. Complete any required fields (indicated by ???).
Ensure the policy is configured as follows:

Policy name Distributed Auto start Save results Correlate by Limit restarts Restart

TADDM_Init_Austin3 Uncorrelated

When selecting Distributed, make sure to assign all monitoring servers (select the *ALL_CMS managed system group).
To save your changes, click Apply or OK.

Making a copy of the original TADDM_Initialization policy template ensures that any future updates to this policy template do not overwrite your customization.

Since initialization policies are uncorrelated and not triggered by a situation, they start with the monitoring server and establish a connection to the TADDM server before the update policies start.

If your environment includes multiple TADDM servers, you can group multiple Configure Tivoli Application Dependency Discovery Manager Integration activities in one initialization policy. These activities do not need to be connected to each other. Choosing to group your Configure Tivoli Application Dependency Discovery Manager Integration activities might be a good idea for administrative maintenance.

The Configure Tivoli Application Dependency Discovery Manager Integration activity defines values that are later used by Send a Tivoli Application Dependency Discovery Manager Update activities.

Update

Update policies forward changes in your monitoring environment to a TADDM server in response to a triggered situation. Update policies contain the Send a Tivoli Application Dependency Discovery Manager Update activity, and might contain other activities such as On Demand Report and Send an email.

Monitoring agents that support TADDM integration provide predefined update policies. Information for the activities within predefined policies might need to be customized for your environment.

You can have multiple update policies. Each policy might perform a different update operation (for example: Create, Update, Move, or Delete).

Complete the following steps to modify any of the policies:

Select the policy, and click Edit Workflow.
Double-click any activity in the Grapher View to edit the parameters.

TADDM integration activities are located on the Extensions tab in the Workflow Editor.

Usage Notes:

For z/OS, ICSF (Integrated Cryptographic Service Facility) must be enabled to allow password encryption.