Page History

...

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

  • 

Updating

Empty the Browser Cache after updating the JOC Cockpit

Just because a new version number is shown at the foot of the browser window, unfortunately does not mean that the browser has fully updated all the library files the JOC Cockpit uses.

You should use Ctrl & F5 as well as emptying the browser cache before starting the JOC Cockpit after an update.

Installation Log Files

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 jetty_base directory.

...