Introduction

• The relocating of Relocating the JOC Cockpit is not a task as easy as relocating Agents and Controllers as the JOC Cockpit installation has includes a number of paths directories that are added to referenced with the Jetty XML configuration files. SoTherefore, instead of Relocating 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
  • workflows that is performed by Agents. However, during migration the
  UI
  • GUI will not be accessible
  as the JOC Cockpit is shut down while migrating so
  • and users cannot monitor workflows or manage
  the
  • inventory items.
• To migrate the JOC Cockpit it is required to perform a fresh installation of the JOC Cockpit and to copy the ./config folder JETTY_BASE/resources 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. location.

Migrating the JOC Cockpit

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

1. Install the JOC Cockpit on the new server.
2. Stop the services for the JOC Cockpit and copy the contents of the ./config folder JETTY_BASE/resources folder of the JOC Cockpit instance which is migrated and paste them to be migrated to the ./config directory respective 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 wellconfiguration 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.
    
3. Start the services service for the JOC Cockpit and use the new server URL to access the JOC Cockpit GUI from your browser.