Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: 'Updating' extended

...

  • 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 $SCHEDULER_DATA\factory.ini file of one of the JobSchedulers, where $SCHEDULER_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 Operation 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 operated..

    • 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

Backup the Audit Log before updating

The audit log will be overwritten during an update. Therefore a backup of the audit log should be made before updating a production system.

See the JOC Cockpit - Audit Log article for more information.

Empty the Browser Cache after updating the JOC Cockpit

...