Table of Contents

Search

  1. Preface
  2. Product Overview
  3. Security
  4. Applications
  5. Partner and Account Information
  6. Events
  7. Event Archiving
  8. User Policies
  9. Schedules
  10. B2B Data Exchange Administrative Tasks
  11. On-boarding Checklist Template
  12. System Properties
  13. Repository Management
  14. Document Management
  15. B2B Data Exchange Utilities
  16. Dashboard and Reports Management

Administrator Guide

Administrator Guide

Import Specification File

Import Specification File

The import specification file contains instructions on which objects to import into the
B2B Data Exchange
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
B2B Data Exchange
. The import and export utility determines whether an object exists in the
B2B Data Exchange
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
B2B Data Exchange
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
B2B Data Exchange
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
B2B Data Exchange
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:
<!-- The import specification requires a particular order of the elements --> <ImportSpecification>    <!-- Default resolution in case a particular object has not been specified. -->    <!-- Specifying ‘default’ here is an error -->    <!-- This element is required -->    <DefaultResolution>cancel</DefaultResolution>    <!-- Definitions of the resolutions per object type.    If none are specified then the empty element tag has to be supplied    -->    <!-- This element is required, but does not need to contain child elements -->    <ObjectTypeResolutions>       <!-- multiple entries are allowed. Be aware that multiple entries       for the same type can result in unpredictable behaviour -->       <ObjectTypeResolution type="flowtemplate">overwrite</ObjectTypeResolution>       <!--The value ‘default’ revers to the default resolution as defined above -->       <ObjectTypeResolution type="account">default</ObjectTypeResolution>    </ObjectTypeResolutions>    <!-- A specific object resulotion for a profile -->    <ObjectResolution type="profile">       <Resolution>reuse</Resolution>       <Name>
ProfileName
</Name>    </ObjectResolution>    <!-- A specific object resulotion for a flow template. In this case the default    resolution of the object type flow template is used. -->    <ObjectResolution type="flowtemplate">       <Resolution>default</Resolution>       <Name>
workflowName
</Name>    </ObjectResolution>    <!-- A specific object resulotion for an account. In this case the default    resolution of the object type account is used. -->    <ObjectResolution type="account">       <Resolution>default</Resolution>       <Partner>
PartnerName
</Partner>       <Name>
AccountNumber
</Name>    </ObjectResolution>
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

0 COMMENTS

We’d like to hear from you!