Migrating an existing installation to a new application server

Use this procedure to migrate from Central Coding 3.1.0.1 to Central Coding 6.2. If you are using Central Coding release 3.1 or earlier, upgrade to release 3.1.0.1 before running this procedure. For more information, see the Central Coding 3.1.0.1 Installation Guide.

Prepare the new server.
For more information, see:
- System Requirements.
- Preparing the Central Coding installation.
If you are running Oracle Database 11.2.0.4, upgrade to Oracle Database 12.1.0.2.
On the old application server, stop Central Coding services and disable all jobs.
If you are also migrating the database server:
1. On the old database server, export the schema files for the Coding, Platform, and Dictionary database users.
2. On the new database server, import the schema files exported during the previous step.
3. Run ApplyHardeningGrantsToSchemas.cmd to grant database users necessary permissions on required packages. The script is located in the Central Coding 6.2 ZIP file in the folder CodingDBSetup\CreateCentralCodingDatabase.
Install the Central Coding application on the new server running Microsoft Windows Server 2012. During the installation, select the options for using the existing Coding, Platform, and Dictionary Database users. For more information, see Installing a Central Coding application server.
Using the Dictionary Loader, recreate the dictionary repository connections.
Make sure jobs are running on the new application server.
If user name/password authentication was configured for calls to the InForm Adapter interfaces prior to migration, a system administrator must re-enter the InForm authentication user credentials in Central Coding 6.2 on the pages where they were previously entered (the System Configuration page or the Study Information page for individual studies).
Uninstall the Central Coding application from the old server.