Page History

...

• 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 data directory will be owned by the JOC Cockpit run-time account.
• Location of log files
  • The installer will try to look up the /var/log directory:
    • If the directory is available then
      • the/var/log/sos-berlin.com/js7/joc directory will be created and will be assigned read/write permissions for the JOC Cockpit run-time account.
      • the $JETTY_BASE/logs symlink will be created that points to the /var/log/sos-berlin.com/js7/joc directory.
    • If the directory is not available then log files will be written to the $JETTY_BASE/logs directory.
  • Alternative configuration
    • Users can manually create the $JETTY_BASE/logs symlink that points to the directory where log files should be stored. The directory should offer read/write permissions to the JOC Cockpit run-time account.
• Location of the PID file
  • The installer will try to look up the /var/run directory. If this is not available then it will look up the /usr/var/run directory.
    • If the directory is available then the/var/run/joc directory or /usr/var/run/joc directory will be created and will be assigned read/write permissions for the JOC Cockpit run-time account.
    • If the directory is not available then the PID file will be written to the $JETTY_BASE/joc.pid file.
  • Alternative configuration
    • The installer will create the ~/.jocrc file in the user's home directory of the JOC Cockpit run-time account.
    • This file can be added the JETTY_RUN environment variable that is assigned the directory to which the PID file will be written. The directory should offer read/write permissions to the JOC Cockpit run-time account.

...