Page History

...

• The JOC Cockpit can only be used to operate JobScheduler Masters in versions 1.11 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.In high availability environments the
• JOC Cockpit can be used with a remote DBMS, requires access to the DBMS that operates the JobScheduler database.
• An JVM 1.8 Statustitle< CONFIRMAn 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 location of the JRE. Statustitle< 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?

...

The JOC Cockpit is available for Linux and Windows operating systems and the same archive can be used for installation on 64-bit and on 32-bit systems. See the Which platforms is JobScheduler available for and what platform support is provided? article for more information. Statustitle@AP: IS ARTICLE CORRECT TARGET?

Download the JOC Cockpit Archive

...

They can be downloaded from:

• the SOS Web Site Download page page 
• the JobScheduler SourceForge page Statustitle< Links to be addedthe JobScheduler Source Forge

Installation Procedure

Preparation

• Unpack the archive JOC Cockpit archive to a suitable directory such as /tmp on Linux systems or C:\temp on Windows.

...

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

    • /opt/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 to specify whether this web server is to be installed and if so, to specify its configuration - i.e. the port(s) it uses - and installation path.
  • The Install JOC ... inclusive including 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 paths to the jetty_base directory are:

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

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

• Step 5 - Choose the DBMS

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

  • 
    
    

• 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 if a problem occurs during installation a warning message will be shown here and a link to the installation log file will be provided.
    
    

• Initial Testing with the JOC Cockpit Login Form

  Note that a  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.

  • 

...

The JOC Cockpit can be uninstalled using the uninstall.cmd script and uninstall.sh scripts saved in the folders:

• on Linux systems:
  
  • /opt/sos-berlin.com/joc/Uninstaller  < PATH TO BE verified
• on Windows systems:
  • C:\Program Files\sos-berlin.com\joc\Uninstaller

...

Files that are not removed during a normal uninstall (i.e. when the checkbox is not ticked) are noted in the File Structure section of this article below.

...

Text TO BE addeD

Anchor
Configuration with Alternative Web Servers Configuration with Alternative Web Servers

Configuration with Alternative Web Servers

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 configured in Step 4 of the installation procedure described above. An alternative web server that is capable of handling Java web applications, such as Tomcat or another Jetty web server, can also be used.

...

• on Linux systems:
  
  • /opt/sos-berlin.com/joc/resources/joc   < PATH TO BE CONFIRMED
• on Windows systems:
  
  • C:\Program Files\sos-berlin.com\joc\resources\joc

...

• on Linux systems:
  
  • /opt/sos-berlin.com/joc/resources/joc   < PATH TO BE CONFIRMED
• on Windows systems:
  
  • C:\Program Files\sos-berlin.com\joc\resources\joc

...

• Program Files
  • sos-berlin.com
    
    • joc
      
      • install (directory with files)
        • install_jetty_base.cmdshortcut.vbs
        • sleep.exe
        • update_jetty_base.cmd
      • jetty (directory with files)
      • jetty_base (symlink)
      • service
        as below plus:
        
      • sos_joc.exe
      sos_jocw.exe
      • Uninstaller (directory, the empty remains after uninstall and full uninstall)
        
        jobscheduler.ico
        • uninstall.cmd
        • uninstaller.jar
      • .jocinstallinformation (file, remains after uninstall)
      • joc_install.xml (file, remains after uninstall)

...