Importing an XML file into an object store

This topic explains in general terms how Enterprise Manager assists with the import process. (See Run the Import Helper for specific instructions.) You start the import procedure from the object store into which you want to import objects.

Updating objects

An important concept to keep in mind regarding the importing of objects is the concept of updates. For the following object classes, you can update the properties of an existing object instead of creating an entirely new object during an import procedure:

ClassDefinition
If the ID of an existing ClassDefinition on the target object store matches the ID of the ClassDefinition on the object being imported, the properties of the existing ClassDefinition are updated with the values of any matching properties on the object being imported. To use this update function, however, the idmImportObjectId flag must be set on the import method; otherwise a duplicate object exception is thrown. In other words, the import process attempts to create new objects with the same symbolic names — violating a uniqueness constraint.

Properties that are updated, in the case of an ID match, which are not dependent object lists:

Properties that are updated, in the case of an ID match, which are dependent object lists:

All other properties are not updated.

PropertyTemplate
If the Id of an existing PropertyTemplate on the target object store matches the Id of the PropertyTemplate on the object being imported, the properties of the existing PropertyTemplate are updated with the values of any matching properties on the object being imported. To use this update function, however, the idmImportObjectId flag must be set on the import method; otherwise a duplicate object exception is thrown.

Properties that are updated, in the case of an ID match, which are not dependent object lists:

 Properties that are updated, in the case of an ID match, which are dependent object lists:

  All other properties are not updated.

  Note that there is special handling for some dependent object lists that are updated as part of an import procedure:

Import Helper

Use the Import Helper tool in Enterprise Manager to choose the XML file you want to import and the location where you want to store the content. For example, you can choose to store content in the object store's database or one of its file stores. During the import process, the Import Helper displays a status screen that shows its progress. The Import Helper checks for duplicate components and does not overwrite an existing object with a duplicate. When encountering a duplicate object, the Import Helper records the duplicate entry as an error in a log file and continues to import objects that haven't already been added to the object store.

The Import Helper provides four tabs that help you define the objects imported, as described below:

Import Options tab

Use the Import Options tab on the Import Helper window to choose the import file. This is an XML file that contains object store definitions created through the Content Engine's export manifest. You can also specify the following options:

Import Items tab

The Import Helper's Import Items tab provides an expandable list of all objects contained in the export file. This list also identifies those associated properties that were not visible from Enterprise Manager's tree view when you created the XML files. By default, the Import Helper selects all objects associated with each object type in the XML file.

You can de-select any of the associated objects you do not want to import into your object store.

Scripts tab

Use the Import Helper's Scripts tab to specify a sequence of scripts to run at various points during the import process. For details, see Adding scripts to the import process.

Advanced tab

The Advanced tab on the Import Helper dialog gives you more control over what to import automatically. Based on the options you select on the Advanced tab, you can import more than one object, even if only a single object was selected on the Import Items tab. Clearing some associated objects can cause errors that the system logs while importing the objects.