Versions Compared

Key

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

...

  • A Java Runtime Environment in version 1.8 or newer is required. For details see the Which Java versions is JobScheduler available for? article.
  • It is necessary that a time service is operated on the server that hosts JOC Cockpit in order to synchronize the system clock's time.
  • Technically the JOC Cockpit can be operated in any Unix environment. However, support for operation of the JOC Cockpit is limited to Linux systems as described in the JS7 - Platforms article.
  • The JOC Cockpit requires access to a database to store inventory and status information, as well as workflow related logs - see the JS7 - Database article.
    • A schema has to be created in the database prior to installation.
    • A user account has to be created that is granted full privileges for the schema.
    • If you intend to use different accounts and privilege sets for setup and for operation of the JOC Cockpit then consider switching Hibernate configuration files after setup (see below) to use an account with limited privileges to select, insert, update, delete and execute permissions for schema objects.
  • Installation of the JOC Cockpit requires administrative privileges in the following situations:
    • for Unix systems
      • the JOC Cockpit installer cannot be executed from the root account but can be executed from a user account that makes use of sudo to acquire privileges:
        • to make the root account owner of the installation directory, for example, in /opt
        • to make the user account owner of the configuration directory, for example, in /var
      • administrative privileges are not required for installation with a user account that owns the installation and configuration directories.
    • for Windows systems
      • the setup requires administrative privileges.

...

  • Performing headless installation of JOC Cockpit on Unix systems without root permissions:

    Code Block
    languagetext
    titleStarting headless installation of the JOC Cockpit on Unix systems without root permissions
    # login as the user account (not as root)
    ./setup.sh -u joc_install.xml
    • All files in the installation and configuration directories will be owned by the user account
  • Performing headless installation of JOC Cockpit on Unix systems from a user account that can acquire root permissions:

    Code Block
    languagetext
    titleStarting headless installation of the JOC Cockpit on Unix systems with root permissions
    # login as the user account (not as root)
    ./setup.sh joc_install.xml
    • The installer will use sudo to acquire root permissions. Execution of the above command by the root account is denied.
    • Files in the installation directory will be owned by the root account, files in the configuration data directory will be owned by the user account as described below.
  • Performing headless installation of JOC Cockpit on Windows systems requires administrative privileges:

    Code Block
    languagetext
    titleStarting headless installation of the JOC Cockpit on Windows systems
    @rem login with an account that can acquire elevated privileges for administrative tasks
    setup.cmd joc_install.xml

...

  • for Unix to the:
    • installation directory: /opt/sos-berlin.com/js7/joc
    • configuration data directory: /var/sos-berlin.com/js7/joc
  • for Windows to the:
    • installation directory:  Program Files\sos-berlin.com\js7\joc
    • configuration data directory: ProgramData\sos-berlin.com\js7\joc

...

  • /opt (Unix installation directory), Program Files (Windows installation directory)
    • sos-berlin.com
      • js7
        • joc (installation directory)
          • .jocinstallinformation (installation response file, remains in place after uninstall)
          • jetty_base (symbolic link to configuration data directory)
          • license.gpl (copy of  (plain text format of license terms for GPLv3 (General Public License) used for the Open Source JS7 - License)
          • license.html (HTML format of license terms for the commercial JS7 - License)
          • license.txt (plain text format of license terms for the commercial JS7 - License)
          • ThirdParty.txt (lists the the 3rd party components and licenses used by JS7)
          • db (directory for DBMS *.sql scripts to populate the database)
            • h2
            • mssql
            • mysql
            • oracle
            • pgsql
          • install (directory with Jetty installer scripts)
          • jetty (directory for Jetty binary files and scripts)
          • lib (directory for user specific configurations)
          • service (directory for operation as a Windows Service)
          • Uninstaller (Uninstaller directory, the empty directory remains in place after uninstall)
            • joc_install.xml (installer response file, remains in place after uninstall)
            • uninstaller.jar (binary file of the uninstaller)
            • uninstall.sh|cmd (script to invoke uninstaller)
  • /var (Unix configuration data directory)ProgramData (Windows configuration data directory)
    • sos-berlin.com
      • js7
        • joc
          • jetty_base (configuration directory)
            • joc_home (symbolic link to installation directory)
            • start.ini (Jetty servlet container configuration file, remains in place after uninstall)
            • archive (directory for JOC Cockpit versions before applying patches, remains in place after uninstall)
            • lib (directory for Java libraries, remains in place after uninstall)
            • logs (directory for log files files, remains in place after uninstall)
            • resources (directory for configuration files, remains in place after uninstall)
              • joc (directory for configuration files, 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 configuration file, remains in place after uninstall if modified, see JS7 - Logging)
                • shiro.ini.active (Shiro configuration file if the JS7 - Shiro Identity Service is used. This file reports the currently active configuration, remains in place after uninstall)
                • shiro.ini-example (Shiro example configuration file if the JS7 - Shiro Identity Service is used)
                • lib (optional directory for JDBC Drivers and licensed binary code)
                • license (optional directory for license certificate files, remains in place after uninstall)
                • xsd (directory for XSD schema files, remains in place after uninstall)
            • temp (directory for temporary files, remains in place after uninstall)
            • webapps (directory for JOC Cockpit installation)
              • joc (directory for JOC Cockpit GUI files and patches)
              • root
  • /home/<user-account> (Unix home directory)
    • .jocrc (user profile script applied on start-up of JOC Cockpit)

...

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

...