Page History

...

• Step 4 - User Data / Install Jetty

  • The default installation path - the jetty_base - for the Jetty Web Server delivered with the JOC Cockpit 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 used to change the installation path of the Jetty delivered with the JOC Cockpit.

  • 

  • If the Jetty delivered with the JOC Cockpit is not to be used then all JOC Cockpit files including logs and resources such as the shiro.ini configuration file will be installed in the following directories:
    • ??? on Linux systems and

      Status
      title < FILE LOCATION TO BE ADDED

    • C:\Program Files\sos-berlin.com\joc on Windows
  • Note that if it another web server is to be used, the 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 next 5th 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, 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.
  • If this file is edited later on and the
    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 this 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 next form: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 provided with the JOC Cockpit has been installed (see Step 4 of the installation procedure above):
  

  • 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 root:root and Shiro Authentication will be active.

    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.

  • 

...

Installation log files are named according to the pattern Install_V[release]_[date&time]_...log where release is the version release number and date and time refer to the installation.

Deinstallation

The .. C:\Program Files\sos-berlin.com\joc\Uninstaller ....

Anchor
Configuration with Alternative Web Servers Configuration with Alternative Web Servers

Configuration with Alternative Web Servers

...