Implementing Content Porter
This section explains the logic—that is, the transfer rules, mappings and dependencies—Content Porter applies when transferring content between different versions of Content Manager.
- Content Porter configuration
This section lists the various overall configuration options available to you in Content Porter. For options to configure one specific export, import or undo process, refer to the user topics. - Skinning DTAP infrastructure
Apply skinning to the Content Manager Explorer user interfaces in your DTAP setup in order to make a clear, visible distinction between the different environments. - Transfer use case
The scenario described in this section provides an example of how an organization can set up the transfer of items between Content Managers. This includes examples of the related infrastructure, organizational groups and business processes. It is not intended to impose a certain infrastructure or security framework on your organization. - Export and import business rules
Exporting from, or importing into, a Content Manager is subject to certain business rules and may sometimes result in data loss. - Transfer business rules
The transfer (export, then import) of content is subject to a number of rules and constraints. - Dependencies
When you export content, not only the items you select are exported, but (by default) also the items on which those selected items depend: the selected items' dependencies. - Troubleshooting Content Porter
Content Porter offers a number of ways to troubleshoot the import or export process—you can expect problems when importing or exporting a large volume of content.