Migrating Composer and Composition Center resources

The EXPORT, IMPORT, and MIGRATE modes are used to migrate Composer and Composition Center resources and security data from one runtime repository to another. The type of migrated data is described in the table below.

Area	Data
Composer	Contains resources used by Composer. You can select whether to include this area in the export.
CompositionCenter	Contains resources used by Composition Center. You can select whether to include this area in the export.
Security	Contains rules, permissions, etc. This area must always be included in the export.

Note:

Jobs are not migrated using Repository Migration Tool. This means jobs must be finished, and queues must be empty before you migrate runtime repository data.

There are two main scenarios for runtime repository data migration:

•	Upgrading to 5.6 – migrate data from the old runtime repository to a new 5.6 runtime repository.

•	Deploying from 5.6 environment A to 5.6 environment B – migrate runtime repository data from one environment to another (e.g. from the Test repository to the Production repository).

To migrate when upgrading from SPx to 5.6

1	Create a new 5.6 runtime repository.

2	Run EXPORT against the SPx repository. See Exporting resources.

3	Run IMPORT against the 5.6 repository. See Importing resources – do not clean up repository before importing.

To migrate from environment A to environment B

1	Run EXPORT against the environment A repository. See Exporting resources.

2	Backup the environment B repository.

3	Run MIGRATE against the environment B repository. See Importing resources – clean up repository before importing.