Importing Extended Rule Libraries

When you import extended rule libraries, the Import option converts an XML file or installable bundle to Sterling B2B Integrator resources format.

Depending on the type of export you used (standard or advanced, default or all versions), the Import option performs the following functions:

• Creates new non-versioned extended rule libraries
• Creates and checks in new versioned extended rule libraries (assigns time/date of the import)
• Updates or preserves existing non-versioned extended rule libraries
• Preserves or appends existing checked-in extended rule libraries
  Note: To prevent the loss or corruption of existing records, preserve and download the backup file of all imports that you conduct.

The standard import:

• Replaces non-versioned records
• Appends to existing versioned resources
• Sets the default according to imported records

Some important general information about importing resources:

• You must manually update imported resources that contain hard-coded, computer-specific information. For example, system paths in scripts must be manually changed to use the new path after importing resources to their new location.
• During import, Sterling B2B Integrator creates a backup file containing records as they existed prior to import. After you import the resources, you can download and preserve the backup file, which is named backup.xml by default.You can change the name of the backup file so that you do not overwrite an existing backup file.

For both non-versioned and versioned resources, the import process creates a new record where none exists. If you are importing an extended rule library to an environment that already contains the same library, you have the option to update the existing library (selecting Yes for the Some objects being imported may exist in the system. Do you wish to update them? parameter) or to preserve the existing library (selecting No for the Some objects being imported may exist in the system. Do you wish to update them? parameter).

For the update option, selecting Yes for the Some objects being imported may exist in the system. Do you wish to update them? parameter is the default option. Depending on whether you are working with versioned or non-versioned resources, different actions occur.

• If you are importing non-versioned extended rule libraries, the update option replaces the existing records.
• If you are importing versioned libraries, the update option appends to the list when versions already exist, incrementing by one, according to the starting point of the import system.

For the preserve existing option (selecting No for the Some objects being imported may exist in the system. Do you wish to update them? parameter) depending on whether you are working with versioned or non-versioned resources, different actions occur.

• Non-versioned resources – If a record (file containing the extended rule library or libraries) already exists, nothing is imported. The import process does not change existing records.
• For versioned resources – The preserve existing option does not change any versions currently in the system, and adds only new versions.