Resolving data conflicts

The import process evaluates differences between the data imported and the data in the target server and helps resolve conflicts between the two.

Ensure that we imported a Java™ archive (JAR) file from your local system.

Difference evaluation generates a list of objects that are found in the import JAR file and in the target system. An administrator can use the list to resolve conflicts on an object-by-object basis. The administrator decides precedence over existing data or by overwriting existing data with the import data. Difference evaluation and conflict resolution are done for both partial and full export types.

Objects that exist in ISIM at the time of the import that are selected in the conflicts summary to be overwritten are updated.

Objects in the uploaded JAR file that are not in ISIM at the time of the import are added.

To resolve conflicts between the data in an uploaded JAR file and the data in the server...

  1. From the navigation tree, click Configure System > Import Data. The Import Data page is displayed, and the Status column of the table indicates whether any conflicts are detected.

  2. In the Status column on the table, click the Conflicts Detected link. The Evaluate Import File page is displayed.

  3. On the Evaluate Import File page, select the check box next to the object to import and override the existing object, and then click Import. Selecting the check box at the top of this column selects all objects.The Import Data page is displayed.

  4. On the Import Data page, click Refresh to update status of the import in the table. The Status column indicates that the import is successful.

The import process commits the data, re-establishes relationships between parent objects and their dependencies. The process places objects in their correct containers in the ISIM organizational chart.

If your session with the ISIM console is idle and times out while conflicts are being evaluated, or if you explicitly log off, then the import process status changes from Processing to Failed - Conflicts not Resolved. If this status change occurs, repeat this procedure so that the data is committed. Typically, user sessions are configured to be idle for up to 10 minutes before timing out.

Do additional import management tasks, or click Close.

Parent topic: Data import and export