Versions Compared

Key

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

Table of Contents

Introduction

  • Relocating a Controller instance refers to moving the Controller instance either to a new server or to a new location on the same server. Relocating a Controller instance will not stop the execution of workflows with Agents. However, if a workflow includes jobs that are executed with different Agents then the workflow will not be completed and will be put on hold as switching of Agents during workflow execution is performed by the Controller.
  • As the Agent passes workflow execution results to the Controller and as the Controller instance is stopped during relocation, job execution results are not updated to the JOC Cockpit. Once the Controller instance is started again (after relocation) then job execution results are updated to the JOC Cockpit History and become visible with the GUI.
  • To relocate a Controller instance it is required to install a new Controller instance and to copy the contents of the ./state folder to that Controller.
  • Before copying folder contents you should first stop the service for the Controller instance as otherwise it will continue to update its journals.
  • After the new Controller instance is started then modify the Controller settings in the JOC Cockpit GUI to point to the new location.

Relocating a Controller

  • Relocating a Controller requires to install a new Controller instance and to copy the ./state directory of the previous Controller instance to the new Controller instance location. Then change the URL from the JOC Cockpit "Manage Controller/Agents" dialog.
  • The ./config folder for the Controller contains the truststore and keystore, therefore, if the Controller instance is operated for HTTPS connections and if you want the new Controller to use HTTPS too, then the new instance might require an individual server authentication certificate that reflects its hostname.

Relocating a Controller Instance's Journal

If ControllerInstance1 is facing an outage then follow the below steps to relocate the Controller instance's journal from ControllerInstance1 to a new ControllerInstance2:

...