JS7 JobScheduler

Space shortcuts

Page tree

Versions Compared

Old Version 3

changes.mady.by.user Kanika Agrawal

Saved on

compared with

New Version Current

changes.mady.by.user Alan Amos

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Introduction

  • The relocating of Relocating the JOC Cockpit is not a task as easy as relocating Agents and Controllers as . This is because the JOC Cockpit installation has includes a number of paths that are added to directories which are referenced by the Jetty XML configuration files. SoTherefore, instead of Relocating relocating the JOC Cockpit, it is called 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
    workflow as the workflow execution is done by Agent
    • workflows which are 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 necessary 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 Installing the JOC Cockpit on the new server, for details see JS7 - JOC Cockpit Installation On Premises.
  2. Stop Stopping the services for the JOC Cockpit Unix daemon or Windows Service and copy copying the contents of the ./config folder JETTY_BASE/resources/joc folder of the JOC Cockpit instance which is migrated and paste them to be migrated to the ./config relevant 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 the 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  
  3. Start the services Unix daemon or Windows Service for the JOC Cockpit and use the new server URL to access the JOC Cockpit GUI from your browser.