Introduction

• Relocating the an Agent refers to the scenario when where the Agent needs to should be moved either to either a new server or to a new location on the same server. The relocating of the agent Relocation of an Agent will stop the execution of workflow for a certain time as we need to copy workflows during the Agent's down-time. Relocation steps include copying the contents of the ./state folder directory to the a new agentAgent installation.
• Before copying the content we need to contents you should first stop the services for the Agent Agents' service as otherwise it will continue to update the its journals. This is an important step ; as otherwise ,the Agent will execute the same workflows should once it be is started later on. This would result in double job execution that which might be harmful depending on the nature of your jobs.
• As the agent Agent does not have any use a database connection so , relocating the agent Agent only requires copying the contents of the ./state directory to be copied and updating the URL of the Agent with the newly installed agent to be updated in the JOC Cockpit user interface.

Relocating an Agent

• The relocating of Agent requires only moving the agentRelocating an Agent requires the installation of a new Agent and copying the Agent's journal from the ./state directory of Agent and changing the URL from . Then the Agent's URL has to be changed in the JOC Cockpit "Manage Controller/Agents view" dialog.
• The ./config folder for the Agent contains the trust-store and key stores so if the agent is running on HTTPS of an Agent installation may contain keystore and truststore files and additional configuration files. Therefore, if the Agent is operated with HTTPS connections and if you want the new Agent also to run on HTTPS then use HTTPS connections as well, the new server should have its own server authentication certificatesAgent may require an individual server authentication certificate that matches the hostname.

Relocating

...

an Agent's Journal

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

1. Ensure that Agent1 has shutdown.
2. Install Shutdown Agent2.
3. Copy the files from the ./state folder directory of Agent1 to the respective folder relevant directory of Agent2. 
4. Start Agent2.
5. Consider Note that the Agent URL is not the same for Agent1 and Agent2.  Therefore the URL has to be updated in the JOC Cockpit.
6. To change the Agent URL, login to the JOC Cockpit.
7. From the main menu select the item "Manage Controllers/Agents".
8. Make sure you edit the existing Agent1 which is not in service.
9. Change the Agent1 URL to point to the Agent2 URL.
10. When workflows are confirmed to work with Agent2 then drop or move the contents of the ./state directory of Agent1. This an important step as otherwise, otherwise Agent1 will execute the same workflows should if it be is started later on. This would result in double job execution that which might be harmful depending on the nature of your jobs.
    
    
    
    

Notes:

• If you use an HTTPS connection connections for Agents then consider that Agent2 might need may require its own individual server authentication certificate. 
  • If Agent1 is operated for with HTTPS , then you can modify the protocol to HTTP and point to a different host provided that this is in line with your security requirements.
  • The same applies vice versa if Agent1 is operated for with HTTP and Agent2 is operated for with HTTPS.
• If you intend to roll back from Agent2 to Agent1 then consider applying repeat the above steps respectivelyprocedure described above, changing the controller instances appropriately.