...

Disabling of Subagents can be used for example to manage maintenance windows on server nodes.

Anchor
delete_subagent delete_subagent

Delete Subagent

Subagents can be deleted only if no jobs are assigned the Subagent Cluster in question.

• Users can apply the Search & Replace function for Agent assignments in a workflow that is available from the JS7 - Workflow Editor.
• Users can apply the JS7 - Inventory Search function to replace Agent assignments across workflows.
• Modified workflows have to be deployed to a Controller to make such changes effective.

Anchor
deploy_agent_cluster deploy_agent_cluster

Deploy Agent Cluster

...

Anchor
add_subagent_cluster add_subagent_cluster

Add Subagent Cluster

For any Subagent the JOC Cockpit automatically creates a Subagent Cluster for the single Subagent.

• This Subagent Cluster is not visible and is not modifiable. It is 
• It is therefore not required to add Subagent Clusters with a single Subagent. In addition, the GUI denies such operations.

To add a Subagent Cluster the Create Subagent Cluster button can be used.

...

The operation to deploy a Subagent Cluster is available from the Deploy button in the right upper corner:

Anchor

...

delete_subagent_cluster

...

delete_subagent_cluster

...

Delete Subagent

...

Cluster

Subagent Clusters can be deleted only if no jobs are assigned the Subagent Cluster in question.

• Users can apply the Search & Replace function for Agent assignments in a workflow that is available from the JS7 - Workflow Editor.
• Users can apply the JS7 - Inventory Search function to replace Agent assignments across workflows.
• Modified workflows have to be deployed to a Controller to make such changes effective

Users have a number of options to organize their Subagent Clusters:

• For each Subagent JOC Cockpit automatically adds a cluster that holds the single Subagent.
  • This allows to assign an individual Subagent to a job should the job be executed with this Subagent only.
  • This Subagent Cluster is not visible and cannot be modified by users.
  • The name of the Subagent Cluster corresponds to the Subagent ID.
• Any number of Subagents can be added to a cluster.
  • Adding more Subagents to a round-robin cluster allows unlimited horizonal scaling.
  • Some might consider it paranoid to add a larger number of Subagents to a fixed-priority cluster, however, users are free to create a chain of Subagents that can replace each other.
• Subagents can be added for both fixed-priority and round-robin scheduling modes within the same cluster.

Users can add the Director Agent to their Subagent Clusters:

• The Primary and Secondary Director Agents each include a Subagent that can be used to execute jobs.
• The Director Subagent can be added to any Subagent Clusters.
• Users can decide not to use the Director Agent for job execution but for orchestration of Subagents only in order to guarantee the highest level of robustness.

Users can apply different strategies to manage operational Agent Clusters and functional Subagent Clusters.

• A single or a few Agent Clusters can be used that each holds a larger number of Subagent Clusters.
  • Each Subagent Cluster selects a number of Subagents.
  • The same Subagents can occur in any number of Subagent Clusters.
  • The same Subagents cannot occur in more than one Agent Cluster.
  • This scenario can be applied for load sharing between server nodes that act for a number of clustered applications.
• A larger number of Agent Clusters can be used that hold a single or a small number of Subagent Clusters.
• Agent Clusters are autonomous and are not related to each other. 
• Each Agent Cluster is assigned an individual Director Agent that is optionally clustered.
This scenario is preferably applied in a situation when communication between a Director Agent and Subagents should be limited to a few servers, for example for use of Agent Clusters in separate network zones.

Assign Subagent Cluster to Jobs

...

Further Resources