Use the TADDM Change Detection Connector to communicate with IBM® Tivoli® Application Dependency Discovery Manager (TADDM) database for directly detecting changes using TADDM Java APIs (TADDM SDK).
TADDM is a management tool that supports configuration items (CIs) and relationships between them. This configuration information is collected through periodic automatic discoveries, which can scan the entire application infrastructure of a business organization. The collected data includes deployed software components, physical servers, network devices, virtual LAN and host data.
When an initial scan is performed, all subsequent discoveries detect new changes, if any, which are occurred in the infrastructure. The TADDM Change Detection Connector directly retrieves these changes without scanning the entire TADDM database.
The TADDM Change Detection Connector is based on TADDM Connector and shares the following common features:
The TADDM Change Detection Connector operates only in Iterator mode.
The TADDM Change Detection Connector detects changes for a specified time interval, for example, from 01 Jan 2010 00:00:00 to 10 May 2010 02:00:00. If the interval is not specified, the connector detects changes from the earliest possible date 01 Jan 1970 00:00:00 and returns everything since then.
In the TADDM Change Detection Connector, the changes are retrieved at discrete points in time. If the waiting period is 180 seconds, the reported changes are shown at the end of this interval, when compared to its beginning. Therefore, if a configuration item is created and updated several times, the output shows a single create and a single update event. Because the content of configuration items is updated at the end of the waiting interval, both the events show the same attributes. If a configuration item is created and subsequently deleted, no event is returned because it did not exist at either end of the waiting interval. If you require a more fine-grained detection, reduce the value of the Sleep Interval parameter.
The TADDM Change Detection Connector provides Delta tagging at the Entry level. This connector sets only the Entry operation depending on the change type.
For example:
*** Start dumping Entry
Operation: delete
Entry attributes:
guid (replace): '30EFCB75FDAF3B3F92274803BAE6FB01'
$classType (replace): 'sys.linux.LinuxUnitaryComputerSystem'
$id (replace): '30EFCB75FDAF3B3F92274803BAE6FB01'
In this example, a deleted model objects, and its Guid is shown. Also, for the added or modified objects, the attribute list is shown. The IdML mode is used in this example.
*** Start dumping Entry
Operation: add
Entry attributes:
$classType: 'sys.ComputerSystem'
$id: 'CBEEDF3618633CDFA56039E39AE833FF',
cdm:Guid: 'CBEEDF3618633CDFA56039E39AE833FF',
cdm:Signature: 'testSignature',
cdm:CreatedBy: 'administrator',
cdm:LastModifiedTime: 1279790297569,
cdm:DisplayName: 'testDisplayName'
The Entry operation can be get or set as shown in the following script.
var entryOperation = work.getOperation(); //get entry operation
work.setOperation("modify"); //set entry operation
work.setOp ("m");
For more information about Delta tagging and other Delta features, see the "Delta Features" section in IBM Tivoli Directory Integrator V7.1.1 Users Guide.
This section describes input schema of TADDM Change Detection Connector.
The following table lists attributes of the Input Map.
Attribute Name | Description |
---|---|
$cycle | Prevents cycles (loops) in the hierarchical Entry model. |
$id | Holds a unique identifier for the item. For example, TADDM Guid or IdML ID. |
$classType | Holds the CDM/TADDM class name of the read item. |
cdm:ManagedSystemName and managedSystemName formats | Explicit attributes
Both the formats can be used depending on the IdML mode. |
cdm-rel:installedOn.cdm-trg:sys.ComputerSystem and parent formats | Implicit attributes
Can be used depending on the IdML mode. |
$mss and its children | Holds MSS information, if available, and its parameter option is enabled. |
$domain | holds Domain attributes which can prove useful in an enterprise TADDM infrastructure. |
ext:attrName and cdm-ext: attrName formats | Extended attributes
Holds additional non-CDM flat data and both the formats are supported. |
This section describes the parameters of TADDM Change Detection Connector.
If this parameter is not specified when writing to TADDM, an appropriate class type is supplied at run time.
To select a supported class, click the Select button in the Configuration Editor.
Also, the TADDM server version and TADDM SDK version must be same. For example, if TADDM 7.1.2 server is used, the TADDM 7.1.2 SDK must be on the same system, where Tivoli Directory Integrator instance, with the TADDM Connector, is running.
Click the Select button in the Configuration Editor to locate the TADDM SDK.
To specify a past timestamp, use the current TADDM server time as a reference point. Click the Check time button to get the current of TADDM server time. If a value beyond the current server time is specified, the current time is used for change detection.
Use this parameter to set the maximum timeout in seconds for the connector to wait for the next change detection. If a value of zero is specified, the connector waits indefinitely or until there are changes in the database. If this parameter is blank, the value zero is considered.
For example, if the poll interval is 180 seconds and the timeout is 300 seconds, the connector checks for changes, waits for three minutes, checks again and exits if there are no changes.
Click the Select MSS button in the Configuration Editor to select an MSS Guid.