Page History
...
Environment Variable | Default Value | SELinux compliant Value | Notes | ||
---|---|---|---|---|---|
Log Files | JS7_CONTROLLER_LOGS | $JS7_CONTROLLER_DATA/logs | /var/log/controller | The sub-directory controller has to be created and assigned permissions for write access by the Controller's run-time account. | |
PID File |
| $JS7_CONTROLLER_LOGS | /var/run/controller | The sub-directory controller has to be created and assigned permissions for write access by the Controller's run-time account. |
Agent
The location of directories used for the Agent is specified with the Agent Start Script agent_<port>.sh
with <port>
being the HTTP port that the Agent is operated for.
...
Environment Variable | Default Value | SELinux compliant Value | Notes | ||
---|---|---|---|---|---|
Log Files | JS7_AGENT_LOGS | $JS7_AGENT_DATA/logs | /var/log/agent | The sub-directory agent has to be created and assigned permissions for write access by the Agent's run-time account. | |
PID File |
| $JS7_AGENT_LOGS | /var/run/agent | The sub-directory agent has to be created and assigned permissions for write access by the Agent's run-time account. |
JOC Cockpit
The location of SELinux related directories is determined by the JOC Cockpit installer.
...
- The installer will use
sudo
to acquireroot
permissions. Execution of the above command by theroot
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.
- the
- If the directory is not available then log files will be written to the
$JETTY_BASE/logs
directory.
- If the directory is available then
- 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.
- Users can manually create the
- The installer will try to look up the
- Location of the PID file
- The installer will check the JOC Cockpit's run-time account using the following precedence:
- The run-time account can be specified with the
<entry key="runningUser" value=""/>
setting in thejoc_install.xml
response file during installation. - The run-time account is identified from the account running the installer.
- The run-time account can be specified with the
- If JOC Cockpit's run-time account is identified
- to be the root account then the installer will check if the
/var/run
directory is writeable to the JOC Cockpit's run-time account and otherwise it will 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.and finally theJETTY_BASE
directory. - to be a non-root account If the directory is not available then the PID file will be written to the $JETTY
JETTY_BASE
/joc.pid file directory.
- to be the root account then the installer will check if the
- Alternative configuration
- The installer will create the
~/.jocrc
file in the home directory of the JOC Cockpit's 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's run-time account. - Consider that use of sub-directories to
/var/run
is discouraged as this is an ephemeral directory that is reverted on server start-up. - Consider to check the
JETTY_HOME/jetty/bin/joc.service
systemd Service File template that is created by the installer and that has to reflect modifications of the PID file location applied after installation.
- The installer will create the
- The installer will check the JOC Cockpit's run-time account using the following precedence:
Overview
Content Tools