You can use the import and export capability for moving objects from one object store to another. An administrator can select the objects to export. Dependencies between objects are detected so that all related objects can also be exported in the appropriate order for import. For example, if a folder is exported, the user can also choose to export all documents in the folder without selecting the documents individually. The folder is exported first, followed by the documents. The export manifest is a list of all the objects that the administrator has requested to export. The user can view and modify this list, and then perform the export operation, which copies the data to an XML file.
Content Platform Engine XML import and export APIs include security information related to objects. For export, the exported XML includes the entire Access Control List for the object. It also contains the owner information for the object. On import, the APIs independently allow importing of the security information and owner. The APIs do not circumvent any security associated with the FileNet® P8 domain or the object store; these permissions are still checked when trying to update security and owner through import.
A security mapping tool is provided that you can use with the XML security import and export feature. Using the tool, you can map security principals in one domain (development, for instance), contained in an exported XML file, to security principals in another domain (production) before import.
During the import process, you can run scripts to perform additional customization. For example, you might want to update the access rights associated with the new document as it is imported. Scripts can run for each object imported or at the beginning and end of the import process.
Content Platform Engine can be configured to import automatically when a new object store is created. For example, an administrator might define a set of properties, such as Employee ID and Department, which must be consistent across all object stores in the enterprise. These can be defined in a single object store and then exported to an XML file. The administrator can then configure the system to automatically create these property definitions every time a new object store is created.