Controllers are used to orchestrate Agents that execute jobs:

  • A Controller is assigned any number of Agents.
  • One or more Controllers can be registered with a single JOC Cockpit instance.

Controllers can be clustered for high-availability, for details about the architecture see JS7 - Controller Cluster

Controller clustering is subject to the agreements of the JS7 - License:

  • Use of Standalone Controllers:
    • available to Open Source License holders and to commercial license holders.
  • Use of Controller Clusters:

Manage Standalone Controllers

The JS7 - Controller Installation On Premises and JS7 - Controller Installation for Containers articles explain the installation of Standalone Controllers.

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

This brings forward the following view:

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

Add Standalone Controller

Users can add a Standalone Controller by clicking on the New Controller button in the right hand upper corner.

This brings forward the following popup window:


  • 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 Controller can be accessed from the JOC Cockpit.
  • Test Connection: It is recommended that the connection between the JOC Cockpit and the Controller is tested.
    • Users should note that firewalls can block access from the JOC Cockpit to a Controller.
    • Use of a Proxy Service might require updating the URL.

Delete Standalone Controller

With deletion of a Controller, all Agents will removed from the Controller and from the JOC Cockpit inventory.

  • Before deleting the Controller from the JOC Cockpit inventory:
    • Any Agents registered with the Controller should be shutdown and their journals should be removed:
      • Agents can act autonomously and might continue to execute workflows for which orders are still available.
      • Agents' journals are located in the state sub-directory of their configuration directory.
    • The Controller instance should be shutdown and its journal should be removed:
      • Controllers act independently of the JOC Cockpit and maintain network connections to Agents.
      • The Controller's journal is located in the state sub-directory of its configuration directory.
  • Deletion of a Controller does not remove workflows and other scheduling objects from the JOC Cockpit inventory.
    • Scheduling objects can be deployed to any connected Controller.

  • No labels