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 so , 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" dialogue. Refer to the Relocating the Controller's Journal article for detailed steps. dialog.
• The ./config folder for the Controller contains the truststore and keystores so keystore, therefore, if the Controller instance is running on operated for HTTPS connections and if you want the new Controller also to run on use HTTPS too, then the new instance might require an individual server authentication certificate that reflects its hostname.

Relocating the 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:

1. Be assured that ControllerInstance1 is not running.
2. Install ControllerInstance2.
3. Copy the files from the ./state folder of ControllerInstance1 to the respective folder of ControllerInstance2.
4. Start ControllerInstance2.
5. Consider that the Controller URL is not the same for ControllerInstance1 and ControllerInstance2. Therefore the URL has to be updated in the JOC Cockpit.
6. To change the Controller URL, log in to the JOC Cockpit.
7. From the main menu select the item "Manage Controllers/Agents".
8. Make sure you edit the existing ControllerInstance which Controller instance that is not in service.
9. Modify the "URL for JOC Cockpit" from the "Register Controller" dialogue dialog box for the Controller instance that is not in service to point to the ControllerInstance2 URL
10. When workflows are confirmed to work with ControllerInstance2 then drop the contents of the ./state directory of ControllerInstance1. This an important step as otherwise, when ControllerInstance1 is started it will forward past orders from its journal to available Agents. This would result in double job execution that might be harmful depending on the nature of your jobs.
    
    
    
    

...