...

• Note that a JOC Cockpit Cluster requires that two or more JOC Cockpit instances have been installed.
  • For details see the JS7 - Installation article.
• The steps for initial operation are the same for all supported platforms:
  • JS7 - On Premises
  • JS7 - Docker Containers
  • JS7 - Cloud Services

JOC Cockpit Cluster Checks

...

Any JOC Cockpit cluster members have to use the same security level Security Level (low, medium, high), see JS7 - Security Architecture, section Secure Configuration.

The JOC Cockpit has to be reinstalled to apply changes to the security levelSecurity Level.

Check Database Connection

...

• Use a different title for each JOC Cockpit instance to better distinguish instances in the dashboard JS7 - Dashboard view.
• Use an ordering of your choice that determines the sequence in which JOC Cockpit instances are displayed in the dashboardDashboard view.

Both settings are made in the joc.properties file, as shown in the following example:

...

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

...

The following chapters can be skipped if a license key and licensed binary code were have been added during installation of JOC Cockpit. The instructions provided here apply when a license key and licensed binary code are to be added or replaced for an existing installation without updating JOC Cockpit from the installer.

Adding a License Key

• The license key can be added during installation of each JOC Cockpit instance.
• The license key can be added later on by saving the license certificate file in the following locationslocation:
  • Unix: JOC Cockpit Configuration Directory 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 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.

...

• Binary code for clustering is available from the js7-license.jar file which is available from the JS7 - Download page.
• By downloading the binary code for clustering you users consent with the license terms for a commercial license of JS7.
• The js7-license.jar file has to be saved in the following locationslocation:
  • Unix: JOC Cockpit Configuration Directory lib/ext/joc sub-foldersfolder
    
    • Default Location: /var/sos-berlin.com/js7/joc//jetty_base/lib/ext/joc
    • A different location for the configuration directory can be specified during installation.
  • Windows: JOC Cockpit Configuration Directory lib\ext\joc sub-foldersfolder
    • Default Location:C:\ProgramData\sos-berlin.com\js7\joc\jetty_base\lib\ext\joc
    • A different location for the configuration directory can be specified during installation.

Handling for

...

Container Installation

Basically the same locations for license key and licensed binary code apply as explained for Unix operating systems in previous sections of this article.

...

• The license key can be added by saving the license certificate file in the following location:
  • /var/sos-berlin.com/js7/joc/jetty_base/resources/joc/license
  • The directory is typically mounted to a Docker a config volume when running the container: for details see the JS7 - JOC Cockpit Installation for Docker Containers article.

Adding Licensed Binary Code

• Binary code for clustering is available from the js7-license.jar file, which is available from the JS7 - Download page.
• By downloading the binary code for clustering you users consent with the license terms for a commercial license of JS7.
• The js7-license.jar file has to be saved in the following location:
  
  • /var/sos-berlin.com/js7/joc/jetty_base/resources/joc/lib
  • The /var/sos-berlin.com/js7/joc/jetty_base/resources/joc directory is typically mounted to a Docker a config volume when running the container: for details see the the JS7 - JOC Cockpit Installation for Docker Containers article article. The lib sub-directory should be created if it does not already exist before saving the js7-license.jar file.

On startup start-up the JOC Cockpit checks the above directory for existence of the js7-license.jar file. If the file is found then:

• the file will be copied to ./jetty_base/lib/ext/joc 
• any existing version of the file in this directory is will be overwritten.

Initial Operation

...

• 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 with:

  • For example, http://myhost:4446. Check that the JOC Cockpit port can be accessed. Note that this might include adding firewall rules to allow access to this port from the computer that you are operating the browser on.

  • After initial installation of the JOC Cockpit the default User Account root and Password root will be available if no changes have been made to the shiro.ini configuration filedefault configuration. Accounts can later on be managed with JS7 - Identity Services.

• Note that the root user is assigned the all role in the default configuration that includes all available permissions.
  See the JS7 - Authentication and Authorization - Configuration article  and JS7 - Authorization articles 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.

...

• Installation
  • JS7 - JOC Cockpit Installation On Premises
  • JS7 - JOC Cockpit Installation for Docker Containers
  • JS7 - Automated Installation and Update
• Operation
  • JS7 - JOC Cockpit - Command Line Operation
• Configuration
  • JS7 - JOC Cockpit Configuration Items