Administrator Guide

10.4.1
- 10.5
- 10.4.0

Back Next

Import Specification File

The import specification file contains instructions on which objects to import into the

Data Integration Hub

repository. You use the sample specification file structure to create the import specification file.

The import specification file defines how to resolve conflicts when an object that you want to import exists in the

Data Integration Hub

. The import and export utility determines whether an object exists in the

Data Integration Hub

based on the object name.

The following table describes the conflict resolution types you can set:

Conflict Resolution Type	Description
cancel	Cancels the import process. No objects are imported.
overwrite	Overwrites the object in the Data Integration Hub repository with the object from the export file. If you choose to overwrite existing objects, the utility performs partial validation during the import process. For example, the utility does not verify whether the user objects have associated categories. Information about missing objects appears in the import log file. If you choose to overwrite objects that do not exist, the utility creates the objects.
reuse	Retains the object in the Data Integration Hub repository if the object name matches the object in the export XML file, and does not import of the object from the export file.
skip	Skips the object in the export XML file and does not check whether the object exists in the Data Integration Hub repository.
default	Applies the conflict resolution that you set at the parent level of the specification file. For example, if you set the object type resolution to reuse , you can create an element for a specific object name and set the resolution type to default . The import and export utility applies the object type resolution to the specific object.

Conflict resolution types are case sensitive.

You can specify the conflict resolution for all objects, for a type of object, or for a specific object. The following elements define the scope of the resolution that you can perform:

DefaultResolution. Applies the conflict resolution you set to all objects to import. You can define set the default resolution to any type except for default.

ObjectTypeResolutions. Applies the conflict resolution you set to objects of the same type. Use the type attribute to specify the object types.

ObjectResolution. Applies the conflict resolution you set to specific object names. Use the name element to specify the object names.

The following example shows the contents of an import specification file that defines the conflict resolution for objects and object types:


<ImportSpecification>
    <!-- If an object already exists then reuse it -->
     <DefaultResolution>reuse</DefaultResolution>
    
    <ObjectTypeResolutions>
	 <!-- Cancel the entire import whenever a conflicting connection is found in the target system -->
	    <ObjectTypeResolution type="dihconnection">cancel</ObjectTypeResolution>
		<!-- Reuse any existing application from the target system -->
	    <ObjectTypeResolution type="dihapplication">reuse</ObjectTypeResolution>
    </ObjectTypeResolutions>
    <ObjectTypeResolutions>
	 <!-- Skip over the connection, these are already defined in the target system-->
	    <ObjectTypeResolution type="dihconnection">skip</ObjectTypeResolution>
  <!-- Cancel the entire import whenever a conflicting workflow is found in the target system -->
   	 <ObjectTypeResolution type="dihworkflow">cancel</ObjectTypeResolution>
  <!--Overwrite any publication-->
     <ObjectTypeResolution type="dihpublication">overwrite</ObjectTypeResolution>
    </ObjectTypeResolutions>

  <!--Overwrite the specific application 'Finance'-->
     <ObjectResolution type="dihapplication">
        <Name>Finance</Name>
        <Resolution>overwrite</Resolution>
     </ObjectResolution>

  <!--Skip the subscription 'HR' during import-->
     <ObjectResolution type="dihsubscription">
        <Name>HR</Name>
        <Resolution>skip</Resolution>
     </ObjectResolution>

<!--Reuse the topic 'FinanceDepartment' during import-->
     <ObjectResolution type="dihtopic">
        <Name>FinanceDepartment</Name>
        <Resolution>reuse</Resolution>
     </ObjectResolution>
</ImportSpecification>

You must use valid XML names in the export specification file. The following table describes the special characters that you must encode:

Special Character	Encoded Character
<	&lt
>	&gt
&	&amp

Rename Saved Search

Table of Contents

Administrator Guide

Administrator Guide

Import Specification File

Import Specification File