Administrator Guide

10.2
- 10.5.3
- 10.5.0
- 10.4.0
- 10.2.3
- 10.2.2 HotFix 1
- 10.2.2

Back Next

Export Specification File

The export specification file contains instructions on which objects to export from the

B2B Data Exchange

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

When the import and export utility exports an object, it exports all the dependent objects to retain the validity of the exported objects.

For example, if you export a workflow, the import and export utility exports associated event attributes.

For example, when you export an application, the utility exports associated publications and subscriptions.

When you export an event monitor, the import and export utility does not export the user accounts configured to receive notification from the monitor.

You can use the (ALL) token to export all object of the same type from the repository. You enter the token instead of the object name.

The following example shows the contents of the export specification file:

<!-- The order of the object selections does not matter (can be in any order)-->
<ExportSpecification>
   <!-- The minumum number of elements is one -->
   <!-- Export MyOwnEventType -->
   <ObjectSelection type="eventtype">
      <Name>MyOwnEventType</Name>
   </ObjectSelection>

   <!-- Export super event status-->
   <ObjectSelection type="eventstatus">
      <Name>SuperEventStatus</Name>
   </ObjectSelection>

   <!-- Export all the event types -->
   <ObjectSelection type="eventtype">
      <Name>(ALL)</Name>
   </ObjectSelection>

   <!-- Export the flow template, that automatically includes the preprocessing
   templates, applications, and event property keys ? -->
   <ObjectSelection type="flowtemplate">
      <Name>SomeFlowTemplate</Name>
   </ObjectSelection>

   <!-- Export a profile with all its dependencies -->
   <ObjectSelection type="profile">
      <Name>Profile_X</Name>
   </ObjectSelection>

   <!-- Export a delayed processing rule -->
   <ObjectSelection type="delayedprocessingrule">
      <Name>DefaultProcessingRule</Name>
   </ObjectSelection>

   <!-- Export a partner and all its dependencies and related objects
   (such as profiles and delayed processing rules) -->
   <ObjectSelection type="partner">
      <Name>IceSave</Name>
   </ObjectSelection>

   <!-- Export of an account, including its depedendencis and related objects -->
   <ObjectSelection type="account">
   <!-- The partner tag is required, as otherwise we cannot be certain to
   select the correct account -->
      <Partner>IceSave</Partner>
      <!-- the name tag now acts as a selector for the account number -->
      <Name>123456789.123456789</Name>
   </ObjectSelection>
</ExportSpecification>

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

Export Specification File

Export Specification File