Limitations Migration Logs Migration Tips

Managing System Migration and Archiving 8-9

8.2.2 Migration Tips

It is important to remember that migration entails the bundling and copying of information about the Oracle Content Server instance. It does not include any of the actual content that is in the Oracle Content Server instance. Archiver is used to export content. You should take care that if you archive specific content and plan to export it to another system, the metadata information for that content is also migrated using the Configuration Migration Utility. When migrating information from one Oracle Content Server instance to another, there is not a merging of information. Migration is an additive process. The exporting configuration bundle of metadata information is added to the metadata that currently exists in the importing Oracle Content Server instance. If metadata information currently exists that matches the metadata being imported, and if the Force Overwrite rule has been selected during import, then duplicate bundles are replaced. For information about the Force Overwrite option, see Section 8.2.3.6, Uploading a Bundle. Configuration Migration Utility administration tasks must be performed using a specific node of a cluster. If you do not use a specific node, then an error might occur because the job number assigned to an action is known only to the node that started the action. You cannot import a configuration on a 6.2 version of the Oracle Content Server instance. The Edit, Preview, and History options will not appear on the bundles options on the Configuration Bundles page on a 6.2 Oracle Content Server instance. If you import a template to use on another Oracle Content Server instance and if the importing system does not have the same metadata fields, you will not be able to use that template for export later. You must upload the template, import the configuration, and then use it for exporting. For details about the import process, see Section 8.2.3.3, Importing a Template.

8.2.2.1 Limitations

Keep the following limitations in mind when using the Configuration Migration Utility: ■ When exporting workflow configuration information, only the workflow definition is exported. The state of the workflow is not exported. ■ If importing and overwriting existing workflows, ensure that you have the same step names for each workflow. ■ If you import a workflow to a new Oracle Content Server instance, the workflow will not retain the same state information as that of the exporting Oracle Content Server instance. For this reason, you should not plan to export active workflows. ■ This utility is not a cloner. It does not synchronize information with another system, it only copies and moves information. ■ This utility cannot be set up to migrate automatically. ■ Errors may arise when migrating docmeta information from earlier versions of the Oracle Content Server instance because of the use of schemas in later versions of the Oracle Content Server instance. ■ You cannot import users from a 6.2 or 7.0 version of the system to a later version due to Archiver limitations. 8-10 Oracle Fusion Middleware System Administrators Guide for Oracle Content Server ■ Migrating the config.cfg file may have errors because some values are not migrated for safety reasons for example, IDC_Name. Others values, such as that for AutoNumberPrefix, are migrated. ■ Migrating components can be difficult because no preference prompts for example, in Folders or RMA and no database tables can be migrated. ■ No support is provided for Publisher projects or for bundles in components.

8.2.2.2 Migration Logs

You can enable migration trace logs to track activity during migration events. The logs are enabled by clicking System Audit Information on the Admin Applets screen or under the Administration tray. In the Tracing Section Information portion of the page, select cmu from the Active Sections menu. Configuration Migration Utility logs will be included in the trace files that are run. To access the logs, click View Server Output from the Actions menu on the page. The Configuration Migration Utility log information is included with other tracing logs that are generated.

8.2.3 Managing Configuration Migration