Page History

...

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

...

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

Add Standalone Controller

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

...

• Title: An individual description that can be searched for.
• URL: The protocol HTTP or HTTPS, host name or IP address and port by with which the Controller is accessible to from the JOC Cockpit.
• Test Connection: It is recommended to test that the connection between the JOC Cockpit and the Controller is tested.
  • Users should consider that firewalls can block access from the JOC Cockpit to a Controller.
  • Use of a Proxy Service might require to adjust adjusting the URL.

Anchor
delete_controller delete_controller

Delete Standalone Controller

With deletion of a Controller any , all Agents are 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.
    • 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 act independently from the 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.

...