Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Delete the existing Agent configuration, for details see JS7 - How to take an Agent out of Operation.
    • This applies to Standalone Agents.
    • Should an Agent Cluster ID be modified then the Agent Cluster has to be deleted. This will delete any included Director Agents and Subagents.
    • Should a Director Agent ID be modified then the Director Agent has to be deleted. This includes to delete both instances of a Director Agent in an Agent Cluster. Subagents can remain in place.
    • Should a Subagent ID be modified then just the Subagent has to be deleted.
  • Add a Standalone Agent and/or Cluster Agent holding the modified ID as explained with chapter Initial Operation of the following articles:
  • Deploy the Agent using the Deploy deploy operation of the related Agent's action menu.
  • Initialize the Agent using the Reset Forced reset forced operation of the related Agent's action menu.
    • This will force the Agent to restart and to drop its journal in the related <agent-data>/state directory.
      • If the operation is applied to a Director Agent, then this will automatically initialize any Subagents of the Agent Cluster.
    • It can take the Controller approx. 60-120s to reconnect to the Agent.
      • The Controller will automatically deploy scheduling objects to the Agent.
      • The Controller will automatically submit orders to the Agent.

If an Agent Cluster is used, then in the Manage Controllers/Agents page navigate to the Agent Cluster's Subagent Cluster, see Manage Subagent Cluster.

  • If the Agent ID of a Director Agent is modified then the Subagent Cluster has to be re-created.
  • If the Agent ID of a Subagent is modified then the Subagent Cluster remains in place but the Subagent holding the previous Subagent ID is removed and the Subagent holding the new Subagent ID has to be added.

Resources