Solving problems before a Content Porter run
When Content Porter performs an import or export, it can encounter different types of problems. You can solve some of these problems without aborting the import or export process. However, during import, certain problems can occur that can not be fixed during the import. It is advisable to prepare for them in advance.
- Problem discovery
- Problem discovery functionality lets Content Porter find mistakes with the import before performing the actual import. This configurable option lets Content Porter identify as many potential problems as possible with an import before actually executing it. Refer to the user topics to learn how to set this option.
- Validation of mappings
- Content Porter can be configured to check the validity of URIs to which you plan to map. If one or more of these URIs are absent from the target system, Content Porter can abort the import before it actually imports any item. Refer to the user topics to learn more about this option.
- Content synchronization
-
When Content Porter imports Components into a Content Manager, it can now try to synchronize the Components against the Schema, even if the Component does not fit the Schema. For example, if the Schema contains an additional optional field that is not specified in the Component, Content Porter can add this field and leave it empty. Refer to the user topics to learn how to switch on content synchronization
- Preventing import problems
-
The following problems require you to abort an import.
Problem Solution Content Porter cannot resolve a mapping in a mapping table If you are importing and using a mapping table, make sure that items you are mapping to actually exist on the destination Content Manager. The BluePrint parent of an item is required and is neither present in the exported content, nor in the destination Content Manager. Transfer BluePrint items along with their parent items. Note: This step must be taken before exporting from the source Content Manager. - Preventing security problems
-
Regardless of whether you export or import, the Content Porter user may run into security problems if he or she does not have administrator-level rights to the source or destination Content Manager, or insufficient access rights on the external data source.
A typical security problem for users with limited rights is that they can transfer (export, then import) the items they select, but do not have the right to transfer the dependencies of these items.
This problem can be resolved in two ways:
- Explicitly filter out the transfer of these dependencies by using dependency filters.
- Set the Update mode for dependencies in the import process to "No".
In both cases, the dependencies must of course be present on the destination Content Manager for the import to succeed.
- Troubleshooting an HTTPS connection
-
If the Content Porter client user attempts to add a Content Manager server machine that uses the HTTPS protocol, the user may experience problems connecting to that server. There are several possible reasons why the Content Porter client application cannot connect to the HTTPS server:
- The HTTPS server has a certificate that has not been signed by a certificate authority that the client machine trusts.
- The name of the server to which the Content Porter client wants to connect does not correspond to the server name on the certificate
- The certificate has been signed by a certificate authority that the client machine trusts, but it has expired.
In all of these cases, the Content Porter client does not consider the HTTPS server a trusted server, and refuses to connect to it. To check if any of these reasons are the cause the failure to connect, the user should attempt to access the server from Internet Explorer. If Internet Explorer prompts the user for a certificate, one of the above reasons applies. To make the Content Porter client consider the server a trusted server, the user's security administrator must eliminate the cause of the specific problem.