Page History

...

• 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 Jetty checkbox specifies whether the Jetty web server should be installed.
  • While the Jetty web server delivered with the JOC Cockpit is installed in the joc_installation_directory - the Jetty configuration files are installed alongside the JOC Cockpit log and configuration files 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 paths to the jetty_base directory are:

    • /home/[user]/sos-berlin.com/joc on Linux systems and

    • C:\ProgramData\sos-berlin.com\joc on Windows.

    

  • 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 the suitable location for their web server as required. See the Configuration with Alternative Web Servers section below for more information.The Java options for Jetty are stored:
  • on Linux systems in the directory:
    • /etc/default/joc . 
  • on Windows systems in the Registry under:
    • HKLM\SOFTWARE\WOW6432Node\Apache Software Foundation\Procrun 2.0\sos_joc\Parameters\Java
  Java Memory options can also be configured by opening the sos_jocw.exe which can be found in the joc_home\service directory.Image Removed
  

• Step 5 - Specify the Reporting DBMS

  • Choose the DBMS to be used by the JOC Cockpit for the Reporting Database.

  • 
    
    
    

• Step 6 - Configure the Reporting Database Connection

  • Specify the parameters for the connection to the Reporting Database. 

  • 

  • It will be 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 JobScheduler. In this case the Reporting Database Tables will be integrated in the JobScheduler Database. This will be described in the next step.

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

    • reporting.hibernate.cfg.xml

    This file can be modified at a later date if required using a text editor. The 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.
     

• Step 7 - Specify the Database Connection Used by the JobScheduler

  • Specify whether a separate connection it to be specified for the JobScheduler Database 

  • 
  • If the JobScheduler(s) and JOC Cockpit share the same database then clicking Next will cause the Installation to proceed to Step 10. This step starts the installation process itself and changes to the configuration are no longer possible.  
  • If the JobScheduler(s) and JOC Cockpit use separate databases then the checkbox in the form should be deselected. In this case, clicking Next will cause the Installation to proceed to the specification of the DBMS and the connection parameters for the JobScheduler database, which are described next.
     

• Step 8 - Specify the JobScheduler DBMS

  • This form is identical to those already shown for the Reporting Database in Steps 5 above.
     

• Step 9 - Configure the JobScheduler Database Connection

  • Specify the parameters for the connection to the JobScheduler Database.

    • The DBMS type can be found in the database configuration for job history section of the $JOBSCHEDULER_DATA/factory.ini file of one of the JobSchedulers to be operated from the JOC Cockpit, where $JOBSCHEDULER_DATA is defined in the JobScheduler - Installation Guide (Section 1.2).
  • 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:
    
    • jobscheduler.hibernate.cfg.xml

  • This file can be modified at a later date if required using a text editor. A JOC Cockpit user will then have to log in again 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.

  • 
    
    
    

...

• Program Files
  
  • sos-berlin.com
    
    • joc
      • install
        • install_jetty_base.cmd
        • shortcut.vbs
        • sleep.exe
        • update_jetty_base.cmd
      • logs
        • Install_ ... .log (files will remain after uninstall)
      • resources
        • joc
          • jobscheduler.hibernate.cfg.xml (remains after uninstall if modified)
          • joc.properties (remains after uninstall)
          • joc.properties-example (only added if joc.properties file is found at installation start)
          • log4j.properties (remains after uninstall if modified)
          • jobscheduler.hibernate.cfg.xml (remains after uninstall if modified)
          • shiro.ini (remains after uninstall)
          • shiro.ini-example (only added if shiro.ini file is found at installation start)
      • service
        • amd64 (directory)

        • ia64 (directory)
        • manager (directory)
        • x86 (directory)
        • install_jetty_windows_service.cmd
        • LICENSE.txt
        • NOTICE.txt
        • RELEASE-NOTES.txt
        • set_java_home_for_jetty_windows_service.cmd
        • start_jetty_windows_service.cmd
        • uninstall_jetty_windows_service.cmd
      • Uninstaller (the empty directory remains after uninstall)
        
        • jobscheduler.ico
        • uninstall.cmd
        • uninstaller.jar
      • webapps
        • joc.war
      • .jocinstallinformation (file, remains after uninstall)
      • joc_install.xml (file, remains after uninstall)

JOC

...

Cockpit Configuration

...

The joc.properties File

The main configuration information for the JOC Cockpit can be found after installation in the joc.properties file.

...

• the log levels, which are set in lines 3 - 5, and 
• the Audit Log file name, which is set in the last line.

Java Options for Jetty

The Java option values for Jetty are stored after installation:

• on Linux systems in the directory:
  • /etc/default/joc . 
• on Windows systems in the Registry under:
  • HKLM\SOFTWARE\WOW6432Node\Apache Software Foundation\Procrun 2.0\sos_joc\Parameters\Java
• Java Memory options can also be configured by opening the sos_jocw.exe which can be found in the joc_home\service directory.

Image Added

Further Resources

• JOC Cockpit - Authentication and Authorization
  
  • Authentication and Authorization - Configuration
  • Authentication and Authorization - Permissions
• JOC Cockpit - Security
  
  • JOC Cockpit - HTTPS Authentication

...