24 Migrating System Configurations
This chapter covers the following topics:
24.1 Understanding the Configuration Migration Utility
The Configuration Migration utility is used with the Archiver to export one Content Server instance configuration to another Content Server instance. While the Archiver is used to migrate content, the Configuration Migration utility exports the configuration and customization of the Content Server instance.
This section describes the structure of the Configuration Migration utility and how it uses templates and bundles. For an overview of this utility and how it compares to other archiving tools, see Introduction to Migration Tools and Components.
24.1.1 Migration Structure
A bundle is a set of configuration information that is packaged into a single zipped file and made ready for exporting to another Content Server instance.
Information is stored in the DomainHome
/ucm/cs/cmu/
instance
/
directory.
The bundles subdirectory contains specific bundles and associated information. The templates subdirectory contains configuration templates which can be used for new export files.
Information is stored in the DomainHome
/ucm/cs/cmu/
instance
/bundles/
directory.
Each configuration bundle is in a separate subdirectory and contains all the relevant files needed to export that bundle.
Information is stored in the DomainHome
/ucm/cs/cmu/
instance
/bundles/UserBundle/
directory.
Within the specific directories, any customization that is unique to the instance in that export (such as customized metadata fields, schemas, and so on) are included in a separate subdirectory.
Information is stored in the DomainHome
/ucm/cs/cmu/
instance
/bundles/UserBundle/usermetadef/
directory.
Figure 24-4 Customization Stored in Directory

Description of "Figure 24-4 Customization Stored in Directory"
The following files are included in these different subdirectories:
File or Directory | Description |
---|---|
bundle directory |
Each bundle has a subdirectory in the |
templates directory |
Contains export rules created from bundles. When a configuration export is created and saved, a name is given to that export and the configuration is stored as a template in the templates directory |
hda files |
Contains definitions and details of customization and other elements of the exported instance. Depending on how the export was defined, information can be bundled into one HDA file or into several. |
24.1.2 About Migration Templates and Bundles
A migration template is a set of configuration options which specify what Content Server items will be exported. For example, a template named FullCSExport may contain all Content Server items (schema, custom metadata, workflows, and so on). Another template named UserCSExport may only contain options that pertain directly to users (security groups, roles, and so on).
These templates are used to create configuration bundles. A bundle uses the template to determine what to export and to create the necessary definition files which will be exported with the Content Server items. The bundle name is used to identify the finished result of an import or an export. The bundled information is put into a zipped file, containing all the necessary definition files.
24.2 Managing Configuration Migration
Migration consists of tasks such as creating migration templates, creating migration bundles, and exporting or importing the configuration.
24.2.1 Creating a Configuration Migration Template
To create a configuration migration template:
After creating the configuration, you can export it and create a bundle for use on another system. For more information, see Exporting a Configuration.
24.2.3 Importing a Template
To import a template from another system for use on the current instance.
24.2.4 Creating a One-Time Export
To create an export template and immediately export the Content Server configuration:
24.2.5 Exporting a Configuration
To export a configuration:
After exporting, the bundle name appears on the Configuration Bundles page, indicating that it has been bundled. A date and time indicator is appended to the configuration name, as in the following example:
Nov23Bundle-idcm-1-20131123T122436
The initial portion of the name is the original bundle name. The instance name follows (idcm
), followed by the date (20131123
for November 23, 2004) and the time (122436
to indicate 12:24:36). From this Import page, you can download the bundle to a new location so it can be uploaded onto another system.
The original template name (Nov23Bundle
) continues to appear on the Configuration Templates page, where it can be re-exported at another time.
24.2.6 Uploading a Bundle
Before a configuration can be imported it must be first uploaded.
To upload a bundle from another Content Server instance:
24.2.7 Importing a Bundle
After a bundle is uploaded and resides on the importing system, it can be imported for use.
To import a bundle:
24.2.8 Downloading a Bundle
A bundle can be downloaded and stored in an easily accessible location for other Content Server instances to use.
To download a bundle:
24.2.10 Viewing Action History
To view the history of migration actions:
- Choose Administration, then Config Migration Admin, then Action History.
- On the Action History page, for each action you can view the name, source, action, start time, and status.
- Using the Actions menu, you can select a specific action history or clear the Action History.
24.3 Migration Tips
It is important to remember that migration entails the bundling and copying of information about the Content Server instance. It does not include any of the actual content that is in the Content Server instance. The Archiver utility 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 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 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 Uploading a Bundle.
Configuration Migration 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 Content Server instance. The Edit, Preview, and History options will not appear on the bundle's options on the Configuration Bundles page on a 6.2 version Content Server instance.
If you import a template to use on another 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 Importing a Template.
24.3.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 Content Server instance, the workflow will not retain the same state information as that of the exporting 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 Content Server instance because of the use of schemas in later versions of the Content Server instance.
-
You cannot import users from a 6.2 or 7.0 version of Content Server to a later version due to Archiver limitations.
-
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 forAutoNumberPrefix
, 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 bundles in components.
24.3.2 Migration Logs
You can track activity during migration events by examining migration trace logs.
To enable Content Server migration trace logs, choose Administration, then System Audit Information. In the Tracing Section Information portion of the page, choose Active Sections, then cmu. 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.