Chapter 1 Understanding Integration Engine 21
The data transfer process
The processing phase
In the processing phase, the transfer of data takes place. This phase begins when
the data exchange is executed, which can be scheduled or event driven.
During the processing phase, the Integration Engine service:
Refreshes the data exchange.
Before data is exchanged, the Integration Engine service checks the Data
Exchange application to determine if any changes were made to the data
exchange definition. If changes were made, the Integration Engine service
updates the loaded data exchange with the new definition.
Starts a separate thread for each data exchange. Each data exchange connects to
data stores.
The Integration Engine service connects to both the source and target data
stores. The Integration Engine service communicates through the AR System
API or BMC Atrium CMDB API to pull data out of and push data into those data
stores, and through the Adapter Developer Kit interface to pull data out of and
push data into the external data store.
Locates data to be exchanged.
The Integration Engine service obtains a list of keys from AR System or BMC
Atrium CMDB and asks the adapter to create a list of keys. The Integration
Engine service converts the keys to a common data type (if necessary) and then
sorts the keys to make sure that they are in the same order so the key lists can be
compared.
Transfers data.
The Integration Engine service compares the keys and determines from the data
exchange definition how new and existing records should be treated. The
Integration Engine service decides on a key-by-key basis whether to create,
update, or delete records. For each key, adapters can be called to read, write,
update, or delete a record.
Disconnects from data stores.
After all keys are processed, the data transfer is considered complete. The
Integration Engine service closes the connection to AR System or BMC Atrium
CMDB and asks the adapter to close the connection to the external data store.
NOTE
The thread remains active, as does the adapter, unless the data exchange is
deactivated in the Data Exchange application or the Integration Engine service is
asked to terminate. In either of those events, the adapter .
dll is released and the
thread terminates.
