Page History

...

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

Start Installation

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

...

• Code Block
  language text title Starting the JOC Cockpit installer on Unix Linux systems
  /tmp/jobscheduler.[release]> ./setup.sh

• Code Block
  language text title Starting the JOC Cockpit installer on Unix Windows systems
  C:\temp\jobscheduler.[release]> setup.cmd

Configuration Forms

• Language Selection

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

  • 

• Step 1 - Welcome Screen

  • 

• Step 2 - Licensing Agreement

  • 

• Step 3 - Target Path for the Installation

  • The default installation paths for the JOC Cockpit are alongside the default JobScheduler program files:

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

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

• Step 4 - User Data / Install Jetty

  • The default installation paths for the Jetty Web Server - the jetty_base - delivered with the JOC Cockpit are lie 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 provided with the JOC Cockpit is not to be used the Shiro.ini and Hibernate files will still be installed - but in a different directory. See the Configuration with Alternative Web Servers section below for more information.

  • 

  • 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 file will be written to the file system. These files can then be moved to the desired location. The default locations for these files are:
    • ./jetty_base/resources on Linux systems and

      Status
      title < FILE LOCATION TO BE Verified

    • jetty_base\resources on Windows systems.

• Step 5 - Choose the DBMS

  • The type of DBMS used by the JobSchedulers operated by the JOC Cockpit is specified in the next form.

  • The database configuration 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 resources folder.
      The default name and location of this 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:

  • 

• 07 Step 7 - No Slide
  longer required
  
  

• Step 8 -

  08

  Installation

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

  • 

• 09

  Step 9 - Processing

  • 

• Step 10 - Completion

  • 

• Initial Testing with the 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 7 of the installation procedure above):
  

  11 JOC Cockpit Login

  • APPLIES ONLY IF JETTY IS INSTALLED WITH 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 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

The JOC Cockpit configuration and installation log information are written to a new log file each time an installation 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.

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 shown in the above series of screen shots (Step 4). An alternative web server, which 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 installed, resource files that will likely be relevant for system administrators - i.e. the shiro.ini file (containing default authentication and authorization information) and the hibernate.cfg.xml file (containing default database configuration information) - will be written to an alternative location. This location is:

• On Windows systems the files will be saved in:
  
  • C:\Program Files\sos-berlin.com\joc\resources
• On Unix systems it will be:
  
  • ...   < PATH TO BE COMPLETED
• In this situation the shiro.ini file and other resources can be moved by the system administrator to the appropriate application directory.

File Structure

Windows

• If JETTY IS INSTALLED:
  • File Structure is:
    • ProgramData\sos-berlin.com\joc
      • > joc_home < bleibt after uninstall
      • logs < bleibt after uninstall
      • resources < bleibt after uninstall
        • hibernate.cfg.xml
        • joc.properties < bleibt after uninstall
        • joc.properties-example < only added if joc.properties file found
        • shiro.ini < bleibt after uninstall
        • shiro.ini-example < only added if shiro.ini file found
      • temp < bleibt after uninstall
      • webapps
      • start.ini < bleibt after uninstall
    • Program Files\sos-berlin.com\joc
      • install
        • see below
      • jetty
      • > jetty_base
      • service
        • as below plus:
          • sos_joc.exe
          • sos_jocw.exe
      • Uninstaller < bleibt after uninstall (empty)
        • jobscheduler.ico
        • uninstall.cmd
        • uninstaller.jar
      • .jocinstallinformation < bleibt after uninstall
      • joc_install.xml < bleibt after uninstall
• If JETTY NOT INSTALLED:
  • File Structure is:
    • Program Files\sos-berlin.com\joc
      • install
        • see below
      • logs
        • Install_ ... .log < bleibt after uninstall
      • resources
        • hibernate.cfg.xml
        • joc.properties < bleibt after uninstall
        • shiro.ini < bleibt after uninstall
      • service
        • amd64
        • ia64
        • manager
        • x86
        • install_jetty_windows_service.cmd
        • LICENSE.txt
        • NOTICE.txt
        • RELEASE-NOTES.txt
        • set_java_home_for_jetty_windows_service.cmd
        • start_jetty_windows_service.cmd
        • uninstall_jetty_windows_service.cmd
      • Uninstaller < bleibt after uninstall (empty)
        
        • jobscheduler.ico
        • uninstall.cmd
        • uninstaller.jar
      • webapps
        • joc.war
      • .jocinstallinformation < bleibt after uninstall
      • joc_install.xml < bleibt after uninstall
  • Contents of C:\Program Files\sos-berlin.com\joc\install folder are:

    Status
    title < FILE FUNCTIONS TO BE DESCRIBED .....

    
    
    • install_jetty_base.cmd
    • shortcut.vbs
    • sleep.exe
    • update_jetty_base.cmd
  • Contents of C:\Program Files\sos-berlin.com\joc\webapps folder are:

    Status
    title < FILE FUNCTIONS TO BE DESCRIBED .....

    • joc.war

...