Introduction

• Initial Operation is performed after installation of the JS7 Agent, Controller and JOC Cockpit.
• Operation of a JOC Cockpit Cluster requires a commercial license, see JS7 - Licensing.
• Tasks include to apply the license key and licensed binary code.

Prerequisites

Initial Operation requires that a JS7 Agent, Controller and JOC Cockpit are successfully installed and are up and running.

• Consider that a JOC Cockpit Cluster requires two or more JOC Cockpit instances to be installed.
  • For details see JS7 - Installation
• The steps for initial operation are the same for any supported platforms:
  • JS7 - On Premises
  • JS7 - Docker Containers
  • JS7 - Cloud

JOC Cockpit Cluster Checks

Check Security Level

Any JOC Cockpit cluster members have to use the same security level (low, medium, high).

To apply changes to the security level JOC Cockpit has to be reinstalled.

Check Database Connection

Any JOC Cockpit cluster members have to use the same database connection.

To apply changes modify the Hibernate configuration file hibernate.cfg.xml:

• Unix
  • Default Location: /var/sos-berlin.com/js7/joc/resources/joc
  • A different location for the configuration directory can be specified during installation.
• Windows
  • Default Location: C:\ProgramData\sos-berlin.com\js7\controller\<controller-id>\config\license
    • where <controller-id> is the unique identifier for the Controller that is specified during installation.
  • A different location for the configuration directory can be specified during installation.
• Find examples for Hibernate configuration from the JS7 - Database article.

Adding License Key and Licensed Binary Code

Customers equipped with a commercial license receive both a license key from SOS and the binary code that allows clustering of JS7 components.

Find below the summary information, for details see JS7 - FAQ - How to apply a JS7 License Key

Adding a License Key

• The license key can be added during installation of each Controller instance and of each JOC Cockpit instance.
• The license key can be added later on by storing the license certificate file to the following locations:
  • Unix: JOC Cockpit Configuration Directory with license sub-folder
    
    • Default: Location /var/sos-berlin.com/js7/joc/resources/joc/license
    • A different location for the configuration directory can be specified during installation.
  • Windows: JOC Cockpit Configuration Directory with license sub-folder
    • Default Location: C:\ProgramData\sos-berlin.com\js7\joc\resources\joc\license
    • A different location for the configuration directory can be specified during installation.

Applying Licensed Binary Code

• Binary code for clustering is available from the js7-license.jar file that is offered from JS7 - Download.
• By downloading the binary code for clustering you consent with the license terms for a commercial license of JS7.
• The js7-license.jar file has to be stored to the following locations:
  • Unix: JOC Cockpit Installation Directory with lib/ext/joc sub-folders
    
    • Default Location: /opt/sos-berlin.com/js7/joc/lib/ext/joc
    • A different location for the installation directory can be specified during installation.
  • Windows: JOC Cockpit Installation Directory with lib\ext\joc sub-folders
    • Default Location: C:\Program Files\sos-berlin.com\js7\joc\lib\ext\joc
    • A different location for the installation directory can be specified during installation.

Initial Operation

Login to JOC Cockpit User Interface

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

  • For example, http://myhost:4446. Please check that the JOC Cockpit port is accessible which might include to add firewall rules to allow access to this port from the computer that you operate the browser for.

  • 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 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.

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.