Versions Compared

Key

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

...

The architecture includes the clustering Agents in the role of Director Agents for restart capabilities and the clustering Agents acting as Subagents for high availability and scalability.

  • The components involved in an Agent Cluster are represented as one Agent to the Controller.
  • A Controller can manage any number of Agents either from different Agent Clusters or as a number of Standalone Agents.

Functional Layer

The architecture allows to define any number of Subagent Clusters that include a Selection and Scheduling Mode of Subagents: 

...

  • In a first position a Director Agent is available. Optionally a second Director Agent can be available.
  • Below the Director Agent the list of Subagents is displayed.

Add Agent Cluster

The Agent Cluster is situated in the operational layer and includes specification of Director Agents and Subagents.

To add an Agent Cluster users can start from the Controller's action menu to which Agents the Agent Cluster should be added:


This brings forward the following popup window:

...

  • Subagent ID: A unique identifier of the Subagent. Uniqueness is applied for all Director Agents and Subagents in the same Agent Cluster. This identifier cannot be changed later on.
  • Title: An individual description that later on can be searched for.
  • URL: The protocol HTTP or HTTPS, host name or IP address and port by which the Subagent is accessible to the Director Agent.

Manage Subagent Cluster

The Subagent Cluster is situated in the Functional Layer and includes specification of logical clusters that make use of Subagents.

To add a Subagent Cluster users can start from the Agent Cluster's action menu to which the Subagent Cluster should be added:

Image Added


This brings forward the following view:

  • The view displays the list of available Subagent Clusters.
  • The indicated status signals that the Subagent Cluster has been deployed or not not deployed.
  • The indicated synchronization status signals that the definition of the Subagent Cluster in the JS7 inventory and the version deployed to the Controller are in sync.

Image Added


The Image Added buttons in the right upper corner allow to toggle between the list view and the card view of Subagent Clusters:

Image Added


When the checkboxes available with each Subagent Cluster are checked then buttons for the following bulk operations become available:

  • Revoke: The Subagent Cluster is revoked from the Controller, i.e. the deployment is undone. The definition of the cluster remains in place and can later on be deployed once again.
  • Delete: The Subagent Cluster is deleted from the Controller and from the JS7 inventory. This operation cannot be undone.
  • Deploy: The Subagent Cluster is forwarded to the Controller and can be used for assignments to jobs.

Image Added