Page History

...

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

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

...

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
    • 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 examples can be foud in the JS7 - Database article.

...

When installing JOC Cockpit then for each instance a title and ordering can be specified that become visible with , which will be shown in the JS7 - Dashboard:

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

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

################################################################################
### If JOC Cockpit is used in a cluster then specify a title to identify which node
### is currently used. Further specify the ordering (Primary <= 0, Standby > 0) for
### display of JOC Cockpit instances with the Dashboard view.

title                        = PRIMARY JOC COCKPIT
ordering                     = 0

...

Adding License Key and Licensed Binary Code

Customers equipped with 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.

Find below the summary information, for details A short description for procedure required to add the licnese key is provided below - for a detailed description, see JS7 - FAQ - How to apply a JS7 License Key

...

The following chapters can be skipped if a license key was and binary code were added during installation of JOC Cockpit. The explanations apply to a situation instructions provided here apply when a license key should and code are to be added or replaced for an existing installation without updating JOC Cockpit.

...

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

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

Adding a License Key

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

...

• Binary code for clustering is available from the js7-license.jar file that , which is offered available 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 at the following location:
  
  • /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 The lib sub-directory lib  should be created if it does not exist then you can create it to store already exist before saving 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

...

• 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 Check that the JOC Cockpit port is accessible which can be accessed. Note that this might include to add adding firewall rules to allow access to this port from the computer that you operate are operating the browser foron.

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

...