Send a Tivoli Application Dependency Discovery Manager Update

Selecting the Send a Tivoli® Application Dependency Discovery Manager Update activity opens a dialog box for entering information required to forward changes in your monitoring environment, discovered through situation events, to a TADDM server.

Tivoli Application Dependency Discovery Manager Alias
The server alias represents a TADDM server. Use the same server alias that you specified in the associated Configure Tivoli Application Dependency Discovery Manager Integration activity. The server alias can be an arbitrary name such as Prod1, Test2, or Austin3.
Operation Type
The operation type determines what type of update is sent to the TADDM server. Select one of the following types appropriate to the situation that triggered the workflow: Create, Update, Move, or Delete.
Request Parameters
The Request Parameters section is used to define a JavaScript Object Notation (JSON) update request that Cloud Pak System Software Monitoring Server sends to the TADDM server. These three fields are included: Key, Value Type, and Value. Monitoring agents that exploit this activity provide policies that include predefined request parameters.
The Key contains a list of common predefined keys. Other valid key values can be entered, but they must be part of the Tivoli Common Data Model (defined in the IBM Multilingual Terminology database).
The Value Type is a fixed list of selectable values.
The Value can be a predefined selected value or a user-defined value. The most common options are displayed.
See Request Parameters for more information.
Insert Variable Data
Specify Situation Attribute or Other value to substitute data from a preceding situation or On Demand activity.

The Situation Attribute button becomes active if the policy contains a "Wait until a situation is true" activity and you select a row cell under Value.

The Other value button becomes active if the user selects a row cell under Value. Selecting this button opens a dialog box that facilitates the substitution of data returned by a preceding On Demand activity, as well as diagnostic information regarding TADDM activities and On Demand activities.

Request timeout
Select the amount of time in seconds you want to allow before a timeout occurs. A timeout occurs when Cloud Pak System Software Monitoring Server doesn't receive a response from the TADDM server. Options (in seconds): 5, 10, 15 (default), 30, 45, 60, 90, 120.
If multiple data items are returned
Your selection here controls how this activity behaves if the triggering situation returns multiple rows of data. The selection should be predefined based on the supported monitoring agent.
If an update request should be sent only for the first situation row, select Execute request once. Otherwise, select Execute request for each row from activity and select either the situation that triggered the workflow or the On Demand activity. Ensure the Continue processing rows on failure option is selected.