...

• Navigate to the JOC Cockpit login window and enter the User Account and Password.
  After initial installation of JOC Cockpit the default User Account and Password of root:root will be available if no changes have been made to the shiro.ini configuration file.

• Note that the root user is assigned the all role in the default configuration that includes any available permissions.
  See the Authentication and Authorization - Configuration article for information about the configuration of other user profiles and authentication methods.

• Note that the JOC Cockpit web service might take a minute to start and to display the login window.
  
  

Register Controller and Agents

Once the JOC Cockpit is login a dialog window appears. This window asks to register a Controller. You will find the same dialog later on from the User -> Manage Controllers/Agents menu.

You have a choice of registering a Standalone Controller or registering a Controller Cluster for high availability (requires JS7 - Licensing).

Register a Standalone Cluster

The standalone Controller is in the scope of JS7 Open source license.

Image Added

Explanation

• The title added to the Controller will be visible on the JS7 - Dashboard View.
• The URL for JOC Cockpit is the URL for the Controller as seen by JOC Cockpit i.e URL of the COntroller by which the JOC Cockpit can connect to the controller. 

Register Controller Cluster

A Controller cluster implements high availability for automated fail-over should a Controller instance be terminated or become unavailable.

Note that the high availability feature of clustering is subject to JS7 - Licensing. Without a license fail-over/switch-over will not take place between Controller cluster members.

Image Added

Explanation

• This dialog allows specifying of the Primary Controller instance, Secondary Controller instance and an Agent Cluster Watcher.
• The title added to the Controller will be visible on the JS7 - Dashboard View.
• Primary and Secondary Controller instances require a URL as seen from JOC Cockpit.
• The URL of the Controller instance has to match the hostname and port that the Controller instance is operated for.
• The Agent Cluster Watcher is required for the operation of a Controller cluster. The Agent is contacted by Controller cluster members to verify the cluster status should no direct connection between Controller cluster members be available.

Register Agents

After the connection between JOC Cockpit and the Controller is established you can add Agents. To register an Agent switch to the Manage Controller/Agents view from the Profile. Click on the Action Menu of the Controller for which the agent needs to be added and select Add Agent.

Image Added

Explanation:

• For each Agent, a unique identifier is specified the Agent ID. The identifier remains in place for the lifetime of an Agent and cannot be modified.
• You can add a name for the Agent that will be used when assigning jobs to be executed with this Agent. The Agent name can be modified later on.
• In addition, you can add alias names to make the same Agent available with different names.
• Add the URL of the Agent.

Configuration

The JOC Cockpit offers a number of configuration items that can be used to configure JOC Cockpit. Find details from the JS7 - JOC Cockpit Configuration Items article.

...