Page History

...

Adding License Key and Licensed Binary Code

Customers possesssing possessing a commercial license will receive a license key from SOS and can download the binary code that allows clustering of JS7 components, see JS7 - Download.

The steps required are summarised summarized below, for details see JS7 - FAQ - How to apply a JS7 License Key

...

• In your browser navigate to the JOC Cockpit URL and enter the User Account and Password. Typically the URL will include the hostname and port that JOC Cockpit has been installed with:

  • For example, http://myhost:4446. Check that the JOC Cockpit port is accessible. This might require adding firewall rules to allow access to this port from the computer that you operate the browser on.

  • After initial installation of JOC Cockpit the default User Account root and Password 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 and posesses possesses all 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.
  
  

...

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

Explanation

• This dialog allows the Primary Controller instance, the Secondary Controller instance and an Agent Cluster Watcher to be specified.
• The title added for each Controller instance will be shown in the JS7 - Dashboard view.
• Primary and Secondary Controller instances require a URL as seen from JOC Cockpit. This URL is used by JOC Cockpit to connect to the relevant Controller instances.
• The URL of the Controller typically includes the hostname and port that the Controller instance is operated for.
• The Agent Cluster Watcher is required for operation of a Controller Cluster. The Agent is contacted by both Controller Cluster members to verify the cluster status should a direct connection between Controller Cluster members not be available.
  • The Agent is assigned an Agent ID which is a unique identifier for this Agent and cannot be modified during lifetime of an Agent. Change of the Agent ID requires the removal and readdition re-addition of the Agent with JOC Cockpit. It is not necessary to uninstall/reinstall the Agent.
  • The Agent Name is a unique identifier that is used for example in the JOC Cockpit Configuration view to assign Agents to jobs. The Agent Name can be modified later on.
  • The Agent URL is the hostname and port for which the Agent is operated.
• Note that the following connections should be accessible and that this might require the addition of firewall rules to allow access to the ports:
  • JOC Cockpit connection to the Primary Controller host and port.
  • JOC Cockpit connection to the Secondary Controller host and port.
  • Primary Controller connection to the Secondary Controller host and port.
  • Secondary Controller connection to the Primary Controller host and port.
  • Primary Controller connection to the Cluster Watcher Agent host and port.
  • Secondary Controller connection to the Cluster Watcher Agent host and port.

...

• The Agent is assigned an Agent ID which is a unique identifier for this Agent that cannot be modified during the lifetime of an Agent. Change of the Agent ID requires the removal of and readdion re-additon of the Agent with the JOC Cockpit. It is not necessary to uninstall/reinstall the Agent.
• The Agent Name is a unique identifier that is used for example in the Configuration view to assign Agents to jobs. The Agent Name can be modified later on.
• In addition, you can add Agent Alias Names to make the same Agent available by different names.
• The Agent URL includes the protocol, the hostname and port for which the Agent is operated.

...