Introduction

• Relocating an Agent refers to the scenario when the Agent should be moved either to a new server or to a new location on the same server. Relocation of an Agent will stop the execution of workflows during the Agent's down-time. Relocation steps include to copy the contents of the ./state directory to a new Agent installation.
• Before copying the contents you should first stop the Agents' service as otherwise it will continue to update its journals. This is an important step as otherwise the Agent will execute the same workflows should it be started later on. This would result in double job execution that might be harmful depending on the nature of your jobs.
• As the Agent does not use any database connection, relocating the Agent requires just to copy the contents of the ./state directory and to update the URL of the Agent in the JOC Cockpit user interface.

Relocating an Agent

• Relocating an Agent requires to install a new Agent and to copy the Agent's journal from the ./state directory. Then change the Agent's URL from the JOC Cockpit "Manage Controller/Agents" dialog.
• The ./config folder of an Agent installation might contain keystore and truststore files and additional configuration files. Therefore, if the Agent is operated for HTTPS connections and if you want the new Agent to use HTTPS connections too, then the new Agent might require its individual server authentication certificate that matches the hostname.

Relocating an Agent's Journal

If Agent1 is facing an outage and should be relocated to Agent2  - on the same server or a different server - then follow the below steps to relocate the Agent's journal:

...