Page History

...

• Language Selection

  • Select the language to be used for the setup: English and German are available.

  • 
    
    

• Step 1 - Welcome Screen

  • 
    
    

• 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 path 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 alongside the default installation path for the JobScheduler program files:

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

      Status
      title < To Verify

    • C:\Program Files\sos-berlin.com\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. 
    
    
  • 
    
    

• 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.
  • The default installation directory for While the Jetty web server delivered with the JOC Cockpit - the jetty_base - generally lies alongside the default JobScheduler configuration and log files (referred to as the $SCHEDULER_DATA directory in the JobScheduler installation manual). The default path for 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 is:

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

      Status
      title < To Verify

    • C:\ProgramData\sos-berlin.com\joc on Windows.
  • The Jetty Base field in the form shown below 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 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 folder.
    The default name and location of the database configuration file are:
    
    • resources/hibernate.cfg.xml

  • 
    
    

...

The JOC Cockpit configuration and installation log information are written to a new log file each time an installation or update is carried out. These log files can be found in the logs folder in the joc_installation_directory.

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.

...

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

If the checkbox is not selected then configuration files will be left in both the JOC Cockpit installation folder and in the Jetty web server installation folder (if installed with the JOC Cockpit).

...