Allow JOC Cockpit to be operated as API Server

Current Situation

• JS7 products are frequently operated in different network zones including
  • a management zone that operates JOC Cockpit with access by users via HTTP/HTTPS,
  • a deployment zone that operates the Controller which orchestrates Agents,
  • one or more application zones that operate Agents to execute jobs in their respective zone.
• Jobs that make use of the JS7 REST Web Service API have to access JOC Cockpit that implements the API.
  • This includes to establish a network connection from an Agent to JOC Cockpit, in other words, from a secure application zone to a less secure management zone.
  • It should not be required for jobs to establish network connections to a less secure zone in order to use the JS7 REST API Service.

Desired Behavior

• JOC Cockpit is offered to be operated as an API Server
  • This excludes availability of the JOC Cockpit GUI.
  • This excludes clustering features for JOC Cockpit instances acting as API Servers.
  • This includes to operate any number of JOC Cockpit instances acting as API Servers. No clustering applies to API Servers as they are idempotent and can be operated redundantly.
• The JOC Cockpit installer offers the option to operate an API Server with the GUI being stripped off and with no clustering for API Server instances.