Page History
...
The 
icon in the JOC Cockpit main menu offers is used to select the Manage Controllers/Agents view:
...
To add a Standalone Agent users can start from the Controller's action menu of the Controller which the Agent should be added to:
...
- Agent ID: A unique identifier of the Agent. A unique ID is required for all Agents registered with the same a 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 with which the Agent can be accessed from the Controller.
...
- 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, once the Agent has been enabled.
Disabling of Agents can be used, for example, to manage maintenance windows on server nodes.
...
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 of an Agent being visible or hidden it can be enabled/disabled with a Controller, see above.
...
- Reset: Any running tasks in an Agent can continue. The Agent does not accept new tasks . With and will restart once running tasks being completed the Agent will restarthave been completed.
- Reset Forced: Any running task in an Agent are will be 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 from a 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 | ||||
|---|---|---|---|---|
|
For In the list view of Standalone Agents when the checkboxes available with each Agent are checked then : buttons for the following bulk operations become available when the checkboxes shown for each Agent are checked:
- Delete: The Agent is deleted from the Controller and from the JS7 inventory. This operation cannot be undone.
- Deploy: The Agent configuration is forwarded to the Controller and can be assigned to jobs.
...
Each Agent is individually assigned to a job.
- The property editor offers allows Agents to select be selected from the list of Agents that can be assigned a job.
- Assignment of Standalone Agents can look like this:
...
Overview
Content Tools