Page History

...

• Step 4 - User Data / Install Jetty

  • The JOC Cockpit requires a Java-capable web server and comes with a Jetty server. Step 4 allows system administrators specify whether this web server is to be installed and if yes, to specify its configuration - i.e. the port(s) it uses - and installation path.
  • The Install JOC ... inclusive 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 below can be used to set the jetty_base directory.
    The default path ispaths to the jetty_base directory are:

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

      Status
      title < To Verify

    • 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 required 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. See the Configuration with Alternative Web Servers section below for more information.
    
    

• Step 5 - Choose the DBMS

  • The type of DBMS used by the JobSchedulers operated by the JOC Cockpit is specified in this step.

    • 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.
  • The name and location of the database configuration file is specified in the joc.properties file, which can be found in the JOC Cockpit resources jetty_base/resources/joc folder.
    The default name and location of the database configuration file are:
    
    • resources/joc/hibernate.cfg.xml

  • 
    
    

• Step 6 - Configure the Database Connection

  • The access parameters for the DBMS used by the JobSchedulers operated by the JOC Cockpit are specified in this step.

    • The DBMS access parameters used can be found in the database configuration for job history section of the $JOBSCHEDULER_DATA\factory.ini file of one of the JobSchedulers, where $JOBSCHEDULER_DATA is defined in the JobScheduler - Installation Guide (Section 1.2).

  • 
    
    

• Step 7 - No longer required
  
  

• Step 8 - Installation

  • Progress of the first part of the installation procedure is shown in this step.

  • 
    
    

• Step 9 - Processing

  • This step shows the progress of the second part of the installation procedure.

  • 
    
    

• Step 10 - Completion

  • The last step of the installation shows a summary of the installation (success/error) and paths to relevant information.

  • 

  • Note that a warning message will be shown and a link to the installation log file provided at this step if a problem occurs during installation.
    
    

• Initial Testing with the JOC Cockpit Login Form

  Note that a  working web server - either the Jetty provided with the JOC Cockpit or another - is required before the JOC Cockpit installation can be tested.
  To test the JOC Cockpit:
  

  • Call the JOC Cockpit login form in a web browser and enter the username and password.

    After a first installation of the JOC Cockpit the default User Name and Password of root:root and Shiro Authentication will be active, if no changes have been made to the shiro.ini configuration file.

    See the Authentication and Authorization Configuration article for information about the configuration of other user profiles and authentication methods.

  • Note that on some systems the web service may take a minute to start and display the login form shown below.

  • 

...