Exporting and importing overview (Enterprise Manager only)

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:
   • Lifecycle Actions
   • Lifecycle policies
   • Choice lists
   • Property Templates
   • Class definitions
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:
   • Event Actions
   • Event Subscriptions
   • Others (Anything that does not fit into the previous groups, including Document Classification Actions, Security Policies)

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 window (in MB). The maximum file size is limited to 10 MB. For example, if the size of the documents node if exported to a single file would be 200 MB, and if the rollover size is set to 10 MB, 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 contains 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:

• C:\Set1_CEExport_Group1_1.xml
• C:\Set1_CEExport_Group2_1.xml
• C:\Set1_CEExport_Group3_1.xml
• C:\Set1_CEExport_Group4_1.xml
• C:\Set1_CEExport_Group5_1.xml
• C:\Set1_CEExport_Group6_1.xml
• C:\Set1_CEExport_Group7_1.xml

Objects that cannot be exported or imported

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

• Object store object (but you can run the Object Store wizard and then import the objects you want).
• File stores (but you can create a file store and use the Move File Store wizard).
• Content cache stores (instead, run the Content Cache Store wizard in the new object store).
• Saved searches (instead, provide them in an accessible network location).
• Global configuration database (GCD) includes markings, add-on features, authentication provider configurations, fixed content device configurations (there is currently no way to move or import FileNet P8 domain resources between FileNet P8 domains; the GCD is created when the new FileNet P8 domain is created, and then its resources must be re-created one by one).
• Document classes that have been mapped to an IBM Content Manager OnDemand application group.

The following objects cannot be imported:

• Document classes whose default storage area is set to a storage area. However, you can clear the default storage area of a document class to allow it to be imported.
• Document classes that have been mapped to a Content Manager OnDemand application group.

Exporting security

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

• Warning: During an export and import of an object that contains security template ACEs from a security policy, FileNet Deployment Manager removes the security template ACEs. If the security template ACEs that are removed are Deny ACEs, access can be granted unintentionally to users or groups that were previously denied access.
• If you import into an object store in the same FileNet P8 domain, or to a different FileNet P8 domain that is configured to the same authentication provider as the first FileNet P8 domain, security permissions are imported.
• If you import into an object store in a different FileNet P8 domain that is configured to a different authentication database from the first FileNet P8 domain, the security permissions are not imported unless this second authentication database has the exact accounts as the first. If the two are not synchronized, Enterprise Manager provides the Security Mapping wizard so that you can include security account mapping between the two authentication databases. You cannot use the Security Mapping wizard to change authentication provider types.

Import restrictions

If content based retrieval (CBR) is enabled on a source object store, take the following precautions before attempting to import documents.

• If the base document class in the source object store is CBR-enabled, verify that the destination object store is enabled and configured for CBR; otherwise, the import fails.

  Importing a CBR-enabled document class results in enabling CBR on the destination object store that is not configured for CBR. Therefore, no documents can be imported because there is no index area configured for the destination object store.

• If you are importing a set of classes in which the base document class is CBR-enabled, verify that all the subclasses are also CBR-enabled. If they are not, the import fails. The import succeeds only if the document class and its subclasses are all CBR-enabled or all CBR-disabled.

  To import a mix of CBR-enabled and CBR-disabled subclasses, you must import the document class and subclasses separately from the document content, as follows:

  1. Export and import the document class and subclasses.
  2. In the destination object store, set the CBR-enabled property as needed for the document class and each of its subclasses.
  3. Export and import the document content for the document class and its subclasses.