Introduction

• Relocating the Agent refers to the scenario when the Agent needs to be moved to either a new server or to a new location on the same server. The relocating of the agent will stop the execution of workflow for a certain time as we need to copy the contents of the ./state folder to the new agent.
• Before copying the content we need to first stop the services for the Agent otherwise it will continue to update the journals. This an important step as otherwise, 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 have any database connection so relocating the agent only requires copying the contents of the ./state directory and updating the URL of the Agent with the newly installed agent in the JOC.

Relocating an Agent

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