Introduction

• Relocating the Controllers refers to move the Controller either to a new server or to a new location on the same server. The relocating of the Controller will not stop the execution of the workflow. 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 the workflow execution results to the Controller and as the Controller is stopped while the process of relocating the controller is in progress so the job execution results are not updated to the JOC Cockpit but 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 the Controller it is required to copy the contents of the ./state folder to the relocated Controller. 
• Before copying the content we need to first stop the services for the Controller otherwise it will continue to update the journals. 
• As the Controllers also does not have any database connection so relocating the agent only requires copying the contents of the ./state directory and updating the URL of the Controller with the newly installed Controller in the JOC.

Relocating a Controller

• The relocating of Controller requires only moving the ./state directory of Controller and changing the URL from the JOC Cockpit Manage Controller/Agents view. Refer to the knowledge base article Relocating the Controller's Journal for detailed steps.
• The ./config folder for the Controller contains the truststore and keystores so if the Controller is running on HTTPS and if you want the new Controller also to run on HTTPS then the new server should have its own server authentication certificates.