Administer Library Objects › How to Prepare the Production Environment for a New Release › Scenario: Export and Import Objects in a Content Package › Import a Content Package

Import a Content Package

Administrators select the Orchestrator, select the target folder, and then invoke the import. If the import result is a content package, it contains a set of baselined objects for the same release. You cannot modify the release version values of objects in an imported content package.

Follow these steps:

1. Click the Library tab.
2. Click Orchestrator and select the target Orchestrator:environment.
3. Right-click the destination folder and select Import.
4. Click Browse and navigate to the location on your local drive where you saved the exported file. Select the exported XML file and click Open.
5. Select how to import an object that has the same name as an existing object in the same path.
   • Select Import to import each object as a new version of the existing object.

     This option is appropriate for an upgrade when you want to keep the history of previous versions.

     Note: If an existing object has the same release version as the imported object, the imported object replaces the duplicated version.

   • Select Do Not Import to stop the import of the object and keeps the existing object.

     If you select this option, the import process lists the objects with conflicting names. If there are conflicts, you can import again to an empty folder. Alternatively, you can rename the object in the source environment and then repeat the export and import. This option is a good choice when the objects being imported are new objects instead of new versions of existing objects.

   • Select Import and Replace to delete the existing object and import the new version of the object as version 0.
6. Select whether to set the version of objects in the import folder to current.
   • Select Set Imported Version as Current to activate the imported version immediately upon import. If the imported object is an upgrade, existing processes that used the previous version of objects now use the imported version. The imported objects can include a process with the operator targets configured in the import environment. In this case, you can verify the updated process without resetting versions.
   • Clear Set Imported Version as Current to defer the setting as current to a manual process. For example, clear this option if the import contains a process where the targets of its operators are not yet defined in this environment.
7. Select whether to make imported Custom Operators available.
   • Select Make Imported Custom Operators Available to automate the setting as available for all imported custom operators.
   • Clear Make Imported Custom Operators Available to retain an unavailable status for imported custom operators and make them available manually one by one.
8. Select whether to publish a custom operator group to the Modules tab.
   • Select Publish Custom Operator Group Configuration if the import includes new custom operators and a new custom operator group and you are importing to a different Domain than the export Domain.
   • Clear Publish Custom Operator Group Configuration in the following cases:
     • The import environment is in the same Domain as the export environment.
     • The imported custom operators are new releases of existing custom operators. In this case, the custom operator groups exist.
     • You prefer that an administrator publish any new custom operator group configurations manually.
9. Click Submit to start the import process.
10. Click OK on the verification of successful import message.

    The package successfully imports to the selected folder. The package also appears in the Content Packages palette in the Operations tab. When you select a content package from the palette, the properties display. The displayed property is the ReleaseVersion value that was set for the folder before it was exported as a Content Package.