Page History
...
- Connections from the JOC Cockpit to Controllers use the JS7 - REST Web Service API and can be secured by HTTPS with TLS/SSL certificates.
If the JOC Cockpit and Controller are operated on the same server and network interface then no HTTPS connection between components products is required.
If the JOC Cockpit and Controller are operated on different servers or network interfaces then this connection should be secured by HTTPS.
- This article describes the steps required to set up secure HTTPS communication from the JOC Cockpit to a Controller. This includes to use a standalone Controller or a Controller Cluster with an active instance and a standby instance.
- See the JS7 - System Architecture article for an overview of components products and connections.
- Follow the instructions in the JS7 - JOC Cockpit HTTPS Connections article to set up secure connections from clients (user browser / REST API client) to the JOC Cockpit.
- See the JS7 - Agent HTTPS Connections article for information about securing the connections between Controller instances and Agents.
...
- A restart of the relevant component product is required to apply modifications to either the the Controller
JS7_CONFIG_DIR/private/private.conffile or to JOC Cockpit configuration files.
...
Overview
Content Tools