Page History

...

• The JOC Cockpit can only be with version used to operate JobScheduler Masters in versions 1.11 JobScheduler Masters and newer. These JobSchedulers have to use a separate schema, user and database to any other JobSchedulers that use the same DBMS because of changes made to the database tables for version 1.11.
• The JOC Cockpit can only be installed alongside a JobScheduler Master version 1.11 and newer.

  Status
  title < CONFIRM DBMS can be on different computer

• An Oracle Java 8 JRE has to be installed if not already installed for the JobScheduler. Note that Oracle Java 9 has not yet (December 2016) been tested with the JOC Cockpit. The JAVA_HOME variable should be set to point to the JRE.

  Status
  title < CONFIRM DBMS can be on different computer

• A web server such as Jetty or Tomcat, which is capable of handling Java web applications is required. This can be the Jetty provided with the JOC Cockpit installation.

  Status
  title < DOES jetty InSTANCE HAVE TO INSTALLED ON SAME COMPUTER?

...

Start Installation

Installation Dialog installation is started as a dialog by clicking on the setup.sh or setup.cmd files.

...

• 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 installation path for the JOC Cockpit is set in the Step 3 form.

  • 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

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

• 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 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 default installation path - the jetty_base - 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 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 a different web server to that delivered with the JOC Cockpit 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 5th 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, 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

  • 
    
    

...

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 .. JOC Cockpit can be uninstalled using the uninstall.cmd script saved in the folder:

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

Starting the uninstaller will open the following form: ....

• Image Modified

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.

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).

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

  StatustitleTo Be Completed

Anchor
Configuration with Alternative Web Servers Configuration with Alternative Web Servers

Configuration with Alternative Web Servers

...

If the Jetty provided with the JOC Cockpit is not to be installed, the 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 procedure. System administrators can then move the shiro.ini file and other resources to the appropriate application directory as required.

...