Concepts: exporting and importing

You can use Enterprise Manager to export Content Engine objects to XML files. You can then import those objects into another object store. This topic consists of the following sections:

Export manifest and rollover size

The import and export process generates multiple export files instead of a single large XML export file. The export manifest is categorized into seven distinct groups. Each group results in separate XML files, provided those objects actually exist in the manifest:

  1. Group 1 contains:
  2. Group 2 contains Folders
  3. Group 3 contains Documents
  4. Group 4 contains RCRs and DRCRs
  5. Group 5 contains Annotations
  6. Group 6 contains Custom Objects.
  7. Group 7 contains:

The export process generates one or more XML files per group depending on the number of elements that are included in the export manifest and the maximum file size as configured in the export options dialog (in MB). The maximum file size is limited to 10MB. For example, if the size of the documents node if exported to a single file would be 200MB, and if the rollover size is set to 10MB, 20 such files are created with file names Set1_CEExport_Group3_1.xml, Set1_CEExport_Group3_2.xml and so on.

Rollover size refers only to size of the metadata included in the export manifest and does not include the size of content files (which is handled by the Content Folder export option).

Users are required to specify the prefix of the export manifest file that will contain the list of file names that are generated in the export process. For example, the export manifest file name might be Set1_CEExport_Manifest.xml and the contents of this file might be:

NOTE   If you move the manifest file or the export files to a different location, remember that the manifest file contains hard-coded path names to the various export files. You must edit the manifest file to reflect the new location before running the Import Helper.

Objects that cannot be exported or imported

Most Content Engine objects can be exported and imported. However, the following cannot be exported:

Exporting Security

You can include security permissions in your XML-based export definition by selecting "Export Security Permissions" while running the Export Options tool. To import these permission successfully, consider the following caveats:

API support

You can also use a FileNet P8 API to export and import objects.