Concepts: exporting and importing
Enterprise Manager enables you 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 export functionality generates multiple export files instead of a single large XML export file. The export manifest is categorized into seven distinct groups. Each group will result in separate XML files, provided those objects actually exist in the manifest:
- Group 1 contains:
- Lifecycle Actions
- Lifecycle policies
- Choice lists
- Property Templates
- Class definitions
- Group 2 contains Folders
- Group 3 contains Documents
- Group 4 contains RCRs and DRCRs
- Group 5 contains Annotations
- Group 6 contains Custom Objects.
- Group 7 contains:
- Event Actions
- Event Subscriptions
- Others (Anything that does not fit into the above groups, including Document Classification Actions, Security Policies)
The export process will generate 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 will be 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, then 20 such files will be created with filenames 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 which will contain the list of filenames that will be generated in the export process. For example, the export manifest filename could be Set1_CEExport_Manifest.xml and the contents of this file could 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
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 will need to edit the manifest file to reflect the new location before running the Import Helper.
Objects that are not exportable/importable
Most Content Engine objects are exportable and importable. However, the following
are not exportable:
- 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 new file store and use the Move File Store
Wizard).
- content cache stores (just run the Content Cache Store Wizard in the new
object store).
- saved searches (simply provide them in an accessible network location).
- GCD - includes markings, AddOns, authentication provider configurations,
fixed content device configurations (there is currently no way to move or
import P8 domain resources between P8 domains; the GCD must be created using
the GCD wizard in the new P8 domain, and then its resources must be recreated
one by one.)
Exporting Security
You can include security permissions in your XML-based export definition by
simply selecting "Export Security Permissions" while running the Export
Options tool. To import these permission successfully, consider the following:
- If you import into an object store in the same P8 domain, or to a different
P8 domain which is configured to the same authentication provider as the first
P8 domain, security permissions will import successfully.
- If you import into an object store in a different P8 domain which is configured
to a different authentication database from the first P8 domain, then the
security permissions will not import successfully unless this second authentication
database has the exact accounts as the first. If the two are not synched up,
Enterprise Manager provides the Security Mapping Wizard which will
let you include security account mapping between the two authentication databases.
This will not let you change authentication provider types (Sun ONE to Active
Directory, for example).
API support
You can also use a FileNet P8 API to carry out export and import.