- Relocating the JOC Cockpit is not a task as easy as relocating Agents and Controllers. This is because the JOC Cockpit installation includes a number of directories which are referenced by the Jetty configuration files. Therefore, instead of relocating the JOC Cockpit, it is referred to as Migrating the JOC Cockpit.
- Migration of the JOC Cockpit to a new server or to a new location will not stop the execution of workflows which are 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 necessary to perform a fresh installation of the JOC Cockpit and to copy the
JETTY_BASE/resourcesfolder contents to the new JOC Cockpit location.
Migrating the JOC Cockpit
The steps to migrate the JOC Cockpit include:
- Installing the JOC Cockpit on the new server, for details see JS7 - JOC Cockpit Installation On Premises.
- Stopping the JOC Cockpit Unix daemon or Windows Service and copying the contents of the
JETTY_BASE/resources/jocfolder of the JOC Cockpit instance to be migrated to the relevant directory of the new installation. This will add the hibernate configuration file for database connections, keystore and truststore files as well as the required configuration files.
- Note: If the JOC Cockpit is installed on the new server then make sure that the JS7 - Database accepts connections from the new server.
- Start the Unix daemon or Windows Service for JOC Cockpit and use the new server URL to access the JOC Cockpit GUI from your browser.