Introduction

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:
  • available to commercial license holders,
  • for details see JS7 - Management of Controller Clusters.

Manage Standalone Controllers

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

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 Controller

To add a Standalone Controller users can start from the New Controller button in the right hand upper corner. 

This brings forward the following popup window:

Explanation:

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

Anchor
delete_controller delete_controller

Delete Standalone Controller

With deletion of a Controller any Agents are 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.
    • An Agent's journal is located in the state sub-directory of its configuration directory.
  • the Controller instance should be shutdown and its journal should be removed:
    • Controllers acts independently from JOC Cockpit and maintain network connections to Agents.
    • A 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.