Mapping execution
To execute an Integration Composer mapping, you must run a script that is located in the bin directory of the Integration Composer installation directory.
As Integration Composer executes a mapping, for each object in the source and target, it creates Java™ source code and compiles the source code. When Integration Composer completes a top-level object, including all its children and reference classes, it imports the data for that object to the database.
If you stop and then restart mapping execution and if a last scan date exists for the source, Integration Composer begins where it left off. Only those objects that were not previously committed to the database are moved. Avoid stopping the mapping if at all possible.
Updates
To determine which object or attribute records to update, Integration Composer uses a last scan time stamp. When Integration Composer processes a new object, it records the data for that source object in the Integration Composer repository. On subsequent mapping executions, Integration Composer compares the last scan date in the repository with the scan date in the source data source. One of these actions is performed:
- If the date for a source object is earlier than or the same as the last scan date in the repository, Integration Composer skips the source instance.
- If the date for an object in the source occurs after the last scan date in the repository, Integration Composer processes the expressions for the source instance. The last scan date in the repository is then updated.
By doing this, Integration Composer ensures that it processes only the objects that changed since the last scan date.
If you modify a mapping and you want to implement the change, you might want all data processed. To accomplish this task, you must delete the last scan history. If you delete the last scan history, Integration Composer imports all the source data that is mapped into the target.
Deletions
For some targets, Integration Composer deletes records when importing data into the target.
When Integration Composer imports Deployed Asset data, components of Computers, Network Printers, and Network Devices are deleted if the corresponding record no longer exists in the source. However, top-level Computer, Network Printer, and Network Device records are not deleted. Data from reference classes, such as Manufacturer and Software in Deployed Assets, is not deleted.
If a top-level object no longer exists in the source and you no longer want the data in the target, you can use the Deployed Assets module applications (Computers, Network Printers, and Network Devices) to delete computer, network device, and printer records from the Maximo® database.
If you use Naming and Reconciliation Service (NRS) to identify deployed assets, Integration Composer uses the NRS integration identifier to determine whether a deployed asset exists in the target database. Deployed assets are considered a match if NRS determines that their NRS properties have the same value for one or more naming rules. For example, the signature value is the same for both deployed assets.
If a match is found and there is an NRS integration identifier conflict (that is, the same identifier exists for both the existing deployed asset and the one being processed), then the existing deployed asset and the associated child assets are deleted. The newly imported deployed asset is added, including the NRS integration identifier.