JS7 JobScheduler

Space shortcuts

Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 17 Next »

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:

  1. Be assured that Agent1 is shutdown.
  2. Install Agent2.
  3. Copy the files from the ./state directory of Agent1 to the respective directory of Agent2. 
  4. Start Agent2.
  5. Consider 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 Agent1 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.



Notes:

  • If you use HTTPS connections for Agents then consider that Agent2 might require its individual server authentication certificate. 
    • If Agent1 is operated for 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 HTTP and Agent2 is operated for HTTPS.
  • If you intend to roll back from Agent2 to Agent1 then consider to apply the above steps respectively.



  • No labels