Performing premigration tasks
Before you begin
Before upgrading your production databases during migration, it is a good idea to clone the databases and use the cloned databases to test the database upgrade. This test method prevents your production databases from being corrupted and you can start your source environment again if required. You can keep your source environment running and do the migration testing in parallel using the cloned databases, as long as you make sure that your test environment is isolated from the production environment. Make sure that the two environments do not use the same Process Center.
After you finish testing migration, configure a new deployment environment that you intend to use as the target production environment. You can clone the latest version of the production database to keep the database data up-to-date, or you can switch your new target deployment environment to point to the source production database when you run the migration.
About this task
This migration procedure is for a single deployment environment. A deployment environment is a logical grouping of clusters that work together as a unit, so a deployment environment might consist of an application cluster and a messaging cluster, or might consist of an application cluster, a messaging cluster, and a support cluster. If you have more than one application cluster, you have multiple deployment environments.
If you have multiple deployment environments in your source version, you must repeat the migration procedure for each deployment environment that you want to migrate. Create different source and target migration properties files for each deployment environment.