Introduction

The relocating of the JOC Cockpit is not as easy as Agents and Controllers as JOC Cockpit installation has a number of paths that are added to the Jetty XML files. So, instead of Relocating the JOC Cockpit, it is called Migrating the JOC Cockpit. Migration of JOC Cockpit to a new server or to a new location will not stop the execution of workflow as the workflow execution is done by Agent. However, the UI will not be accessible as the JOC Cockpit is shut down while migrating so users cannot monitor or manage the inventory items.
To migrate the JOC Cockpit it is required to perform a fresh installation of the JOC Cockpit and copy the ./config folder contents to the new migrated JOC Cockpit. As the JOC Cockpit ./config folder not only includes the details about the database configuration but also the truststores as well.

Migrating the JOC Cockpit

The steps to be followed to migrate the JOC Cockpit are:

Install the JOC Cockpit on the new server.
Stop the services for the JOC Cockpit and copy the contents of the ./config folder of the JOC Cockpit instance which is migrated and paste them to the ./config directory of the new installation. This will not only add the hibernate files of the database configurations to the new server but will also add the truststores as well.
Note: If the JOC Cockpit is installed on the new server then make sure that your database accepts the connection from this new server.
Start the services for the JOC Cockpit and use the new server URL to access the JOC Cockpit.