The CS Export Tool runs in 2 phases. See the CS Export flow diagram topic for a flowchart that details the export process:
For additional information on CS Export Restartability, See the CS Export restartability topic for details:
For the Folders, Documents and Versions phase, both content and Metadata give full details. Metadata will always produce an XML detail log. The metadata XML log is fed into the Content Engine Import API for the creation of the doc classes, and custom properties. The Content Engine Import is not used for the export of folders, docs and versions.
NOTE The CS Export Tool export phases do not modify any part of the source Content Services system.
The metadata phase exports all doc classes, CVLs and custom properties to the target Content Engine object store. Doc classes are added as child classes of CS Export Document Base Class. Content Services system properties that do not map to native Content Engine DocVer/CVL properties are placed into custom properties on this base class.
Here are the steps the CS Export Tool follows:
The following table shows Property to Content Engine Custom Property Relationships.
CSProperty | CSDatabase | CECustomProperty |
---|---|---|
Item::Item ID | ELEMENT.E_NAME | CS Original Document ID |
Item::Original Filename | ELEMENT.E_ORG_FILENAME | CS Original Filename |
Item::Keywords | ELEM_KW | CS Original Keywords |
Item::Comment | ELEMENT.E_COMMENT | CS Original Item Comment |
Version::Comment | VERSION.V_COMMENT | CS Original Version Comment |
Version::Version ID | VERSION.V_NAME | CS Original Version |
Version::Checkin Date | VERSION.V_CREATE_DATE | CS Original Creation Date |
For every document class in the source Content Services system there are system properties that do not map to native Content Engine system properties. For example, each version moved from Content Services contains a version branch and version number. For Content Engine to maintain all of this information, a custom property is required.
All such system properties for Content Services versions and documents will be added to the CS_Export_Document_Base_Class in Content Engine. The CS_Export_Document_Base_Class will be the parent class for every document class exported from Content Services.
The Folders and Documents phase migrates selected folders and documents from the source Content Services library to the target Content Engine object store using the Content Engine API. This phase proceeds as follows:
The tool queries the source Content Services system for documents based on document classes and folders the user has selected for export.
This information is primarily held in the ELEMENT and VERSION tables of the Content Services database. Keyword and other list properties are retrieved from the Content Services database in separate queries. Slightly different SQL commands are issued for Oracle and SQL Server databases with and without named instances.