Product Knowledge Base

Space shortcuts

Page tree

Versions Compared

Old Version 40

changes.mady.by.user Alan Amos

Saved on

compared with

New Version 41

changes.mady.by.user Andreas Püschel

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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.
  • JOC Cockpit requires access to the DBMS that operates the JobScheduler database.
  • An JVM 1.8 has to be installed. 
    The JAVA_HOME variable should point to the location of the JRE.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. Statustitle< DOES jetty InSTANCE HAVE TO INSTALLED ON SAME COMPUTER?JDK or JRE..

Operating Systems

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.

...

  • 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

    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 tested.
    To test the JOC Cockpit: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.

...