You can import entities as a background job or in the foreground. The background job runs on the Data Archive server instead of on the Enterprise Data Manager client machine. You can select whether or not to continue processing on error. You can also select the enhanced import option and choose whether or not to update the existing entity.

If you selected enhanced export when you exported the entity, select enhanced import when you import the entity. Selecting enhanced import allows you to import the entity to the environment without corrupting any data. In addition to importing the entity, you can choose the option to update the entity if the entity already exists in the target environment. When you update the existing entity, the import job updates any metadata changes to that entity. The job deletes all of the entity steps and tables and then reinserts them. If you do not choose to update an existing entity, any metadata changes to the entity are ignored.

When you use enhanced import and choose to update the existing entity, Data Archive first verifies that the entity has not been implemented in either an archive or retirement project, or in a Data Discovery operation. If the entity has already been implemented in a project or a Data Discovery operation, you receive a message that the entity will not be updated.

You must import segmentation entities for smart partitioning from the

Segmentation

tab. You cannot import or export segmentation entities from the

Data Archive

tab.

By default, the import job uses enhanced import. To change the behavior, configure the following properties in the

conf.properties

file:

#informia.enable.enhanced.import=Y
Enables enhanced import for entities and custom product family versions. Default is Y. Valid inputs are Y and N.
When this property is set to Y, you are unable to de-select the enhanced import option when you import the entity.
#informia.enable.traditional.import=N
Enables traditional import for entities and custom product family versions. Default is N. Valid inputs are Y and N.
When these properties are set to N in the
conf.properties
file, you are unable to select the corresponding options when you import the entity.

To perform any import operations, a user must have the "import metadata" role assigned in Data Archive. The Administrator user is assigned this role by default, but other users must be assigned this role. For more information on the import metadata role, see the chapter "Security" in the

Data Archive Administrator Guide

.