Page History

...

• Agent ID: A unique identifier of the Agent. Uniqueness is applied 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 which the Agent is accessible to the Controller.

Anchor
deploy_agent deploy_agent

Deploy Standalone Agent

With the configuration of an Agent being completed the Agent can be deployed to its Controller.

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

Anchor
enable_disable_agent enable_disable_agent

Enable/Disable Standalone Agent Agent

Agents can be disabled and enabled. They are enabled by default.

...

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

Anchor
delete_agent delete_agent

Show/Hide Standalone Agent

Agents can be hidden to prevent them

• from being assigned to jobs in the Configuration view,
• from being considered with the Agent Component Status and Agent Cluster Status widgets in the Dashboard view.

Independently from an Agent being visible or hidden it can be enabled/disabled with a Controller, see above.

Anchor
delete_agent delete_agent

Reset Standalone Agent

Agents can be reset in case of problems during initial operation or to re-assign Agents to a different Controller.

• Reset: Any running tasks in an Agent can continue. The Agent does not accept new tasks. With running tasks being completed the Agent will restart. After re
• Reset Forced: Any running task in an Agent are killed. The Agent does not accept new tasks. The Agent drops its journal and restarts with a new journal.
  • Dropping the Agent's journal means that it looses its memory. This operation can be used to seize an Agent, i.e. to assign it a different Controller.
  • This operation should be used with care, for example if an Agent that is assigned a Controller in a production environment is taken over by a Controller of some different environment.
• After restart of a reset Agent the Controller will deploy scheduling objects such as workflows and will submit orders as assigned the Agent.

Anchor
delete_agent delete_agent

Delete Standalone Agent

...

• 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 changes effective.

...

With the configuration of an Agent being completed the Agent can be deployed to its Controller.

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

Anchor
bulk_agent bulk_agent

Bulk Operations on Standalone Agents

...