JS7 JobScheduler

Space shortcuts

Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Introduction

Any number of Agents can be used to execute jobs with a JS7 Controller.

  • Use of Standalone Agents:
    • available to Open Source License holders and to commercial license holders.
  • Use of Agent Clusters is subject to the agreements of the JS7 - License:

Manage Standalone Agents

The JS7 - Agent Installation On Premises and JS7 - Agent Installation for Docker Containers articles explain the installation of Standalone Agents.

The  icon in the JOC Cockpit main menu offers to select the Manage Controllers/Agents view:


This brings forward the following view:

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

Add Standalone Agent

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


This brings forward the following popup window:


Explanation:

  • 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 Conroller.

Enable/Disable Standalone Agent 

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

  • 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 next job executions.
    • For example, after a restart, with the Agent being enabled then orders will automatically continue in the workflow.

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

Delete Standalone Agent

Agents can be deleted only if no jobs are assigned the Agent 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 changes effective.

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.

Bulk Operations on Standalone Agents

For the list view of Standalone Agents when the checkboxes available with each Agent are checked then buttons for the following bulk operations become available:

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

Assign Standalone Agents to Jobs

Each Agent is individually assigned to a job.

  • The property editor offers to select from the list of Agents that can be assigned a job.
  • Assignment of Standalone Agents can look like this:



  • No labels