...

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

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

Handling for Installation on premises

The following chapters can be skipped if a license key was added during installation of JOC Cockpit. The explanations apply to a situation when a license key should be added or replaced for an existing installation without updating JOC Cockpit.

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.

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

Handling for Docker® Installation

Basically the same locations for license key and licensed binary code apply as explained for Unix operating systems with the previous chapters.

However, there is no access to the container's file system before running the container which makes it impossible to add or replace licensed binary code before JOC Cockpit is started.

Adding a License Key

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

Adding 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:
  
  • /var/sos-berlin.com/js7/joc/jetty_base/resources/joc/lib
  • The directory /var/sos-berlin.com/js7/joc/jetty_base/resources/joc typically is mounted to a Docker config volume when running the container, for details see JS7 - JOC Cockpit Installation for Docker Containers. If the sub-directory lib does not exist then you can create it to store the js7-license.jar file.

On startup 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 overwritten.

Initial Operation

Login to JOC Cockpit User Interface

...