Introduction

Relocating the JOC Cockpit is not a task as easy as relocating Agents and Controllers as the JOC Cockpit installation includes a number of directories that are referenced with the Jetty XML configuration files. Therefore, 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 workflows that is performed by Agents. However, during migration the GUI will not be accessible and users cannot monitor workflows or manage inventory items.
To migrate the JOC Cockpit it is required to perform a fresh installation of the JOC Cockpit and to copy the JETTY_BASE/resources folder contents to the new JOC Cockpit location.

Migrating the JOC Cockpit

The steps to migrate the JOC Cockpit include:

Install the JOC Cockpit on the new server.
Stop the services for the JOC Cockpit and copy the contents of the JETTY_BASE/resources folder of the JOC Cockpit instance to be migrated to the respective directory of the new installation. This will add the hibernate configuration file for database connections, keystore and truststore files as well as required configuration files.
- 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 service for JOC Cockpit and use the new server URL to access the JOC Cockpit GUI from your browser.