JS7 JobScheduler

Space shortcuts

Page tree

Versions Compared

Old Version 20

changes.mady.by.user Andreas Püschel

Saved on

compared with

New Version 21

changes.mady.by.user Andreas Püschel

Saved on

Key

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

...

  • the shiro.ini and joc.properties files from an earlier installation will not be overwritten.
  • an existing hibernate.cfg.xml database configuration file will be considered during update and the settings will be suggested as default values. This file will be deleted and a new version of the file will be stored to the joc_home directory.
  • an update of JOC Cockpit will not overwrite any existing configuration files. However new versions of the joc.properties and shiro.ini files with the names joc.properties-example and shiro.ini-example will be stored to the resources\joc folder, alongside the original files.

Initial Operation

Deinstallation

The Having completed the installation or update of the JS7 JOC Cockpit you can start the JOC Cockpit either manually or from its Unix daemon/Windows Service, see JS7 - JOC Cockpit Command Line Operation.

A number of JOC Cockpit instances can be operated as a passive cluster with the first JOC Cockpit instance started acting as the primary cluster member and any additional JOC Cockpit instances acting as standby cluster members. The role of the primary cluster member is decided by the order by which JOC Cockpit instances are started.

  • Consider that operating a JOC Cockpit cluster for high availability requires a commercial license, see JS7 - Licensing.
  • The installation of JOC Cockpit Cluster instances follows the standard operating procedures explained above, there is no difference in installation considering the roles of primary cluster member and standby cluster members. 
  • Consider the following information about initial cluster operation:

Deinstallation

The JOC Cockpit can be uninstalled using the uninstall.cmd and uninstall.sh scripts available from the following locations:

  • For Unix systems:
    • /opt/sos-berlin.com/js7/joc/Uninstaller
  • For Windows systems:
    • C:\Program Files\sos-berlin.com\js7\joc\Uninstaller

Unix Systems

be uninstalled using the uninstall.cmd and uninstall.sh scripts available from the following locations:

  • For Unix systems:
    • /opt/sos-berlin.com/js7/joc/Uninstaller
  • For Windows systems:
    • C:\Program Files\sos-berlin.com\js7\joc\Uninstaller

Unix Systems

The uninstall script on Unix systems runs in headless mode. The uninstall script will start the Uninstaller and remove both the installation directory, configuration directory and respective sub-folders. 

...

If the checkbox is not selected, configuration files will be left in both the JOC Cockpit installation folder and the Jetty servlet container installation folder (if installed with the JOC Cockpit).

Automated Startup and Shutdown

For Unix systems startup and shutdown configurations apply that are executed by the root account e.g. from /etc/init.d scripts and by use of systemd.

  • The JOC Cockpit will start for the user account that is specified during installation. The JOC Cockpit start script jetty.sh will switch to this account independently from the fact that the start script is executed e.g.  by the root account.
  • For use with systemd find a sample service file from ./bin/joc.service-example file.

For Windows systems operation of JOC Cockpit by a Windows Service is recommended as such services can be configured to start/stop automatically on server startup and shutdown.

Startup and Shutdown

For Unix systems startup and shutdown configurations apply that are executed by the root account e.g. from /etc/init.d scripts and by use of systemd.

  • The JOC Cockpit will start for the user account that is specified during installation. The JOC Cockpit start script jetty.sh will switch to this account independently from the fact that the start script is executed e.g.  by the root account.
  • For use with systemd find a sample service file from ./bin/joc.service-example file.

For Windows systems operation of JOC Cockpit by a Windows Service is recommended as such services can be configured to start/stop automatically on server startup and shutdown.

  • Consider to assign a service account to the JOC Cockpit service with the Windows Service Panel.
  • Consider to allow the JOC Cockpit service to be automatically started on server startup.

Initial Operation

Having completed the installation or update of the JS7 JOC Cockpit you can start the JOC Cockpit either manually or from its Unix daemon/Windows Service, see JS7 - JOC Cockpit Command Line Operation.

A number of JOC Cockpit instances can be operated as a passive cluster with the first JOC Cockpit instance started acting as the primary cluster member and any additional JOC Cockpit instances acting as standby cluster members. The role of the primary cluster member is decided by the order by which JOC Cockpit instances are started.

  • Consider that operating a JOC Cockpit cluster for high availability requires a commercial license, see JS7 - Licensing.
  • The installation of JOC Cockpit Cluster instances follows the standard operating procedures explained above, there is no difference in installation considering the roles of primary cluster member and standby cluster members. 
  • Consider the following information about initial cluster operation:
  • Consider to assign a service account to the JOC Cockpit service with the Windows Service Panel.
  • Consider to allow the JOC Cockpit service to be automatically started on server startup.

Further References

...