Page History

...

• The JOC Cockpit can only be installed alongside a JS7 controller
• The JOC Cockpit needs access to the database to store inventory information, status information and workflow related logs. The database is required for restarting capabilities with the JS7 - Cluster Service.
• A JVM Java Runtime Environment starting from version 1.8 has to be installed. is required. For details see Which Java versions is JobScheduler available for?

Troubleshooting Information

• If a MySQL DBMS is being used by the JobScheduler, then the MySQL wait_timeout setting that rules the max. the lifetime of idle connections should be checked and if necessary extended.
  • The default wait_timeout for MySQL is relatively short and the JOC Cockpit cannot keep the connection busy over longer periods of time without user interaction - for example, overnight. 
  • See the JOC Cockpit - Troubleshooting - Database Connection to MySQL unavailable after idle timeout article for instructions about how to change the MySQL DBMS wait_timeout setting. 
• Find more hints on possible installation problems from the JOC Cockpit - Troubleshooting section.

...

The JOC Cockpit can be operated with HTTPS. However, due to problems often experienced complexities with certificate validation, we do not recommend configuring the JOC Cockpit to use HTTPS during the initial installation and configuration procedure. Instead, we recommend that the JOC Cockpit is installed and tested with HTTP and the default Shiro authentication and that . HTTPS connections and , if required, optionally LDAP authentication is can be added in a second step. See the JOC Cockpit - Authentication and Authorization and JOC Cockpit - HTTPS Authentication articles for more information.

...

where release is the release number.

These The archives can be used to install the JOC Cockpit either as from a dialogue or as a batch process and for headless installation for both 32 and 64-bit systems.

They The archives can be downloaded from:

• the SOS Web Site the JS7 - Download page 
• the JobScheduler SourceForge page

...

• Step 2 - Licensing Agreement

  • The License Agreement shown in Step 2 of the installation has to be accepted before installation can take place.

    
    
    

• Step 3 - Target Path for the Installation

  • The path to the installation directory for the JOC Cockpit program files - referred to later in this page as the joc_installation_directory - is set in this step.

  • The default installation paths for the JOC Cockpit are:

    • /opt/sos-berlin.com/js7/joc on Linux systems and

    • C:\Program Files\sos-berlin.com\js7\joc on Windows.
  • Users can use the Step 3 installation form shown below to specify their own installation path for the JOC Cockpit if required. 
    
    
    
    
    

• Anchor
  jetty-base jetty-base

  Step 4 - Jetty Installation & Configuration

  • The JOC Cockpit requires a Java-capable web server and comes with a Jetty server. Step 4 allows system administrators to specify whether this web server is to be installed and if so, to specify its configuration - i.e. the port(s) it uses, installation path, memory pool, etc.
  • The Install JOC ... including the Jetty checkbox specifies whether the Jetty web server should be installed.

  • Default Paths

  • While the Jetty web server delivered with the JOC Cockpit is installed in the joc_installation_directory, which was configured in the previous step - the Jetty configuration files are installed in the jetty_base directory. The Jetty Base field in the form shown in the screenshot can be used to set the jetty_base directory. 
    • The default path to the jetty_base directory on Linux systems leads to the user's home directory:
      • e.g. /home/sos/sos-berlin.com/js7/joc
    • Log files are saved by default in:
      

      • /var/log/sos-berlin.com//js7/joc on Linux systems.

    • The default path to the jetty_base directory and log files on Windows systems is: 
      • C:\ProgramData\sos-berlin.com\js7\joc .

        
  • Note that if If the Jetty delivered with the JOC Cockpit is not to be installed and either an alternative Jetty installation or another web server is to be used, then relevant configuration files for such a server such as the shiro.ini and joc.properties files will still be written to the file system. These files can then be moved by the system administrator to a suitable location for their web server as required. See the Configuration with Alternative Web Servers section below for more information.

• Step 5 - JOC Configuration

  • The JS7 JOC Cockpit can be installed in a cluster. So if the JOC Cockpit is installed as a cluster it is required to provide a title to the JOC. By default the title is joc, this can be modified as per the user.
    
    
    
    
  • The security level for the signing mechanism can be added at the time of JOC Cockpit installation for a security level used for the signing of deployment objects such as workflows. See the Secure Configuration Article for more information. The JS7 JOC Cockpit provides three types of signing mechanisms:
    • Low: This mechanism is easy to use as it does not require any user interaction for the signing operation to be performed. 
    • Medium: This mechanism is similar to the low signing mechanism except for the fact that the private key stored with the current user's profile is used for the signing of configuration objects.
    • High: This mechanism has the highest security level and this requires any configuration objects to be exported and to be signed individually outside of JOC Cockpit.
      
      

• Step 6 - Database Management System

  • Choose the DBMS to be used by the JOC Cockpit for the database system.

  • The database connection settings can be either species directly or can be provided by hibernate configuration file. If the settings are specified directly then it is required to choose the database system otherwise the hibernate configuration file path can be specified after checking the option with hibernate configuration file.
    
    
    
    

  • The database system is specified in the upper selection on this form. It is recommended that the box in the centre of the form remains checked so that the script which creates and fills the necessary database tables can be executed. 
    
    

• Step 7 - Database connection Configuration

  • Specify the parameters for the connection to the DatabaseDatabase. 
    
    
    
    

  • It will probably be obvious from the names given to the parameters in the screenshot above that the values are for a database to be used by the JS7 JOC Cockpit.

  • The database configuration for the JOC Cockpit is written to an XML file during installation and saved in the jetty_base/resources/joc folder. The default name of the database configuration file is:

    • hibernate.cfg.xml

    This file can be modified at a later date if required using a text editor. The JS7 JOC Cockpit service will then have to be restarted before changes made to this file are implemented.

  • The name and location of the database configuration file itself is specified in the joc.properties file, which can also be found in the jetty_base/resources/joc folder.
    
    

...