Integration Composer assets reconciliation using alternate keys and the NRS GUID
alucches 2700012QJC Visits (1491)
IBM Tivoli Integration Composer moves and transforms data from discovery tool databases into the Maximo database as deployed assets. Integration Composer relies on designated alternate key values to determine whether the deployed asset already exists in the Maximo database. If the deployed asset already exists, the non key properties are updated if necessary. If the deployed asset does not exist in the Maximo database, a new record is inserted.
The algorithm limited to alternate key values may produce multiple records of the same deployed asset in the Maximo database. The Tivoli Naming Reconciliation Service (NRS), a component of Data Integration Service (DIS), provides centralized control to identify these assets. Once an asset has been processed by an application using the service, a GUID (Globally Unique Identifier) is assigned to the asset.
Integration Composer uses the data it has about the deployed asset to register and get a GUID and uses the GUID to determine whether the deployed asset already exists in the Maximo database. The NRS GUID is stored as part of the deployed asset data.
For more information about the NRS and asset reconciliation, see this wiki article.