JS7 JobScheduler

Space shortcuts

Page tree

Versions Compared

Old Version 12

changes.mady.by.user Andreas Püschel

Saved on

compared with

New Version 13

changes.mady.by.user Andreas Püschel

Saved on

Key

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

...

  • /opt (Unix) Program Files (Windows)
    • sos-berlin.com
      • js7
        • joc (installation directory)
          • install (directory with Jetty installer scripts and *.sql files to populate the database)
            • install_jetty_base.cmd
            • update_jetty_base.cmd
          • jetty (directory for Jetty binary files and scripts)
          • jetty_base (symbolic link to configuration directory)
          • service (directory for operation as a Windows Service)
          • Uninstaller (Uninstaller directory, the empty directory remains in place after uninstall)
            • uninstall.sh|cmd
            • uninstaller.jar
          • .jocinstallinformation (installation response file, remains in place after uninstall)
          • joc_install.xml (installer response file, remains in place after uninstall)
  • /var (Unix), ProgramData (Windows)
    • sos-berlin.com
      • js7
        • joc
          • jetty_base (configuration directory)
            • archive (directory with filesfor JOC Cockpit versions before applying patches, remains in place after uninstall)
            • lib (directory with filesfor Java libraries, remains in place after uninstall)
            • logs (directory with for log files files, remains in place after uninstall)
            • patches (directory with filesfor patch files (*.zip), remains in place after uninstall)
            • resources (directory for configuration files, remains in place after uninstall and (empty) after full uninstall)
              • joc (directory with for configuration files, remains in place after uninstalluninstallinstall)
                • license (directory for license certificate files, remains in place after uninstall)
                • xsd (directory for XSD schemas, remains in place after uninstall)
                • hibernate.cfg.xml (Hibernate configuration file for database access, remains in place after uninstall if modified)
                • joc.properties (JOC Cockpit configuration file, remains in place after uninstall)
                • log4j2.xml (Log remains log configuration file, remains in place after uninstall if modified)
                • shiro.ini.active (Shiro configuration file reporting the currently active configuration, remains in place after uninstall)
                • shiro.ini-example (only added if shiro.ini file is foundShiro example configuration file)
          • temp (directory with for temporary files, remains in place after uninstall))
          • webapps (directory for JOC Cockpit files that are extracted from the deployed joc.war file)webapps
          • start.ini (Jetty servlet container configuration file, remains in place after uninstall)



Directory Layout if the Jetty Servlet Container is not Installed

...

If the Jetty servlet container included with JOC Cockpit is not to be installed, then the installer will check if a jetty_base symlink from a previous installation is found in the jetty_home directory. Particularly relevant for system administrators is the shiro.ini.active file (containing authentication and authorization settings) and the joc.properties file (containing e.g. database configuration informationJOC Cockpit installation settings).

  • If configuration files are found then they will not be overwritten or removed.
  • Default configuration files will be written to the file system in the joc_home directory.
  • System administrators can move the configuration files to the appropriate directory of their servlet container as required.

...

With a fresh installation the installer will not find an existing Jetty servlet container and will store the resources directory for the joc application by default to the following location:

...

  • 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 the update and the settings will be suggested as default values. The 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 new or old 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.

...

  • Navigate to the JOC Cockpit login form in a browser window and enter the User Account and Password.

    After initial installation of JOC Cockpit the default User Account and Password of root:root will be available if no changes have been made to the shiro.ini configuration file.

  • Note that the root user is assigned the all role in the default configuration which that includes all any available permissions.
    See the Authentication and Authorization - Configuration article for information about the configuration of other user profiles and authentication methods.

  • Note that the JOC Cockpit web service may might take a minute to start and to display the login formwindow.

Configuration

The JOC Cockpit includes certain offers a number of configuration items which that can be used to configure JOC Cockpit. Details about how to configure JOC Cockpit the article Find details from the JS7 - JOC Cockpit Configuration Items can be followed article. 

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

Windows systems

Starting the uninstaller will open display the following form window on Windows systems:



Selecting the "Force the deletion of C:\Program Files\ ...." checkbox will cause the uninstall script to remove boththe program and configuration files and folders.

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

...

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 only in by which JOC Cockpit instances are started.

The installation of the JOC Cockpit instances follows the standard operating procedures described explained above, there is no difference in installation consider considering the roles of primary cluster member and standby cluster members. 

...

Installation with other servlet containers:

...