Page History

...

Use of Standalone Agents:
- is available to Open Source License holders and to commercial license holders.
Use of Agent Clusters:
- is available to commercial license holders,
- for details see JS7 - Management of Agent Clusters.

...

The view is grouped in Controllers (indicated by testsuite and standalone).
For each Controller separate Separate lists of Standalone Agents and Cluster Agents are displayed for each Controller.

Add Standalone Agent

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

This brings forward the following popup window:

...

Agent ID: A unique identifier of the Agent. Uniqueness A unique ID is applied required for all Agents registered with the same Controller. This identifier cannot be changed later on.
Agent Name: The name of an Agent is used, for example, when assigning the Agent to jobs. Similarly to the Agent ID, the Agent Name has to be unique but can be changed later on.
Title: An individual description that can be searched for.
URL: The protocol HTTP or HTTPS, host name or IP address and port by with which the Agent is accessible to can be accessed from the Controller.

With Once the configuration of an Agent being has been completed the Agent it can be deployed to its ControllerControllers.

An Agent can only be used only after deployment to a Controller.
Changes to an Agent, for example, if the Agent's URL is changed, require to be deployedthat the Agent is redeployed.

...

When an Agent is disabled then it is no longer considered for job execution.
- At the point in time of disabling the Agent will continue to complete any tasks running for jobs.
- No new tasks are added to a disabled Agent.
- Any newly added orders will wait for the Agent to become available and enabled.
When a disabled Agent is enabled then it is automatically considered for the next job executions.
- For example, after a restart, with the Agent being enabled then orders will automatically continue in the workflow.

...