Page History

...

• Step 4 - User Data / Install Jetty

  • The JOC Cockpit requires a Java-capable web server and comes with a Jetty server.
  • The Step 4 installation form allows system administrators to specify whether the Jetty Web Server web server delivered with the JOC Cockpit should be installed and if this is the case, to specify its configuration and installation path.
  • The default installation directory for the Jetty Web Server delivered with the JOC Cockpit - the jetty_base - lies alongside the default JobScheduler configuration and log files (referred to as the $SCHEDULER_DATA directory in the JobScheduler installation manual):

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

    • C:\ProgramData\sos-berlin.com\joc on Windows.
  • The Jetty Base field in the form shown below can be is used to change the installation path of the Jetty delivered with the JOC Cockpit.

  • 

  • Note that if If the Jetty delivered with the JOC Cockpit is not to be used then all JOC Cockpit files will be installed in the following directories:??? on Linux systems and Statustitle< FILE LOCATION TO BE ADDED
  • C:\Program Files\sos-berlin.com\joc on Windows
  Note that if a different web server to that delivered with the JOC Cockpit and either an alternative Jetty installation or another web server is to be used, the 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 desired location. 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 the Step 5 form.

    • 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 folder.
    The default name and location of the database configuration file are:
    
    • resources/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 the 6th form.

    • 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

  • The installation form shows the progress of the first part of the installation procedure.

  • 
    
    

• Step 9 - Processing

  • The installation form shows the progress of the second part of the installation procedure.

  • 
    
    

• Step 10 - Completion

  • 
    
    

• Initial Testing with the JOC Cockpit Login Form

  This test is only available after installation of the JOC Cockpit if the Jetty web server Note that a  working web server - either the Jetty provided with the JOC Cockpit has been installed (see Step 4 of the installation procedure above)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 will be 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 it usually takes one or two minutes for the web service to start (only on Win ?) and the login form shown below to appear.

  • 

...

Ticking the "Force the deletion of C:\PRogram Files ...." checkbox will cause the uninstall script to remove all the files and folders in the Program Files folder.

...

These files contain the configuration information for from the last JOC Cockpit and Jetty web server installations.

...

The JOC Cockpit installation procedure contains the option of installing and using the Jetty Web Server that is included in with the JOC Cockpit installation archive. This option was shown configured in Step 4 of the above series of screen shots (Step 4)installation procedure described above. An alternative web server , which that is capable of handling Java web applications, such as Tomcat or an own Jetty server, can also be used.

If the Jetty provided with the JOC Cockpit is not to be installed, a resources folder, containing files that will likely be relevant for system administrators - i.e. the shiro.ini file (containing default authentication and authorization information) and the joc.properties file (containing default database configuration information) - will still be written to the file system. The locations of these files will depend on whether or not a Jetty web server was previously be written to locations described in Step 4 of the installation procedure above. The exact locations will depend on whether the installation program finds an older Jetty installation within the JOC Cockpit installation path specified in Step 3 of the installation procedurealready existing JOC Cockpit resources directory. System administrators can then move the shiro.ini file and other resources to the appropriate application directory as required.

...