Page History
...
- Log file location:
logs
sub-directory of the JOC Cockpit installation. Jetty Log
Main Log Log File jetty.log
Log Rotation with each (re)start Log Retention d Purpose The log file holds log output created on start-up of the servlet container. If the Jetty servlet container won't start then this is the log file to check for errors. Also, it may contain errors due to misconfiguration of the ./resources/joc/log4j2.xml
JOC Cockpit Log
Main Log Debug Log Log File joc.log
joc-debug.log
Log Rotation daily daily Log Retention 30d 30d Purpose The log file holds log output created by the JOC Cockpit application. This log file includes detailed information for problems occurring during operation of JOC Cockpit, e.g. with database connections, . Audit Log
Main Log Log File audit.log
Log Rotation monthly Log Retention unlimited Purpose The JS7 - Audit Log stores information about any changes to the state of objects, such as deploying workflows, cancelling and suspending orders etc. Note that information from the audit log file can be subject to compliance requirements.
Authentication Log
Debug Log Log File authentication-debug.log
Log Rotation daily Log Retention 30d Purpose This log is available for debug output only. It provides detailed information about login to JOC Cockpit including connections to LDAP Directory Services for authentication.
Connection Pool Log
Debug Log Log File connection-pool-debug.log
Log Rotation daily Log Retention 30d Purpose This log is available for debug output only. It provides detailed information about session management of the connection pool that handles database connections.
- Service Logs
Main Log Debug Log Log File service-cleanup.log
service-cleanup-debug.log
Log Rotation daily daily Log Retention 30d 30d Purpose The service cleans up entries from the order and task history, deployment history, daily plan history and audit log. Main Log Debug Log Log File service-cluster.log
service-cluster-debug.log
Log Rotation daily daily Log Retention 30d 30d Purpose The service operates the JOC Cockpit cluster and performs switch-over and fail-over operations when required. Main Log Debug Log Log File service-dailyplan.log
service-dailyplan-debug.log
Log Rotation daily daily Log Retention 30d 30d Purpose The service plans orders from schedules and submits orders to Controllers. Main Log Debug Log Log File service-history.log
service-history-debug.log
Log Rotation daily daily Log Retention 30d 30d Purpose The service receives events about order state transitions and log output of underlying jobs from Controllers and adds them to the history.
Log4j2 Configuration Files
Default Locations
The Log4j2 configuration file log4j2.xml
is available from the following default locations for each JS7 component:
Windows | Unix | |
---|---|---|
Controller | C:\Program Files\sos-berlin.com\js7\controller\lib\log42j.xml | /opt/sos-berlin.com/js7/controller/lib/log4j2,xml |
Agent | C:\Program Files\sos-berlin.com\js7\agent\lib\log42j.xml | /opt/sos-berlin.com/js7/agent/lib/log4j2,xml |
JOC Cockpit | C:\ProgramFiles\sos-berlin.com\js7\joc\jetty\lib\log42j.xml | /opt/sos-berlin.com/js7/joc/jetty/lib/log4j2,xml |
Note:
- Changes to the log4j2.xml file from the above locations will be lost if newer versions of JS7 components are installed.
Optional Locations
The Log4j2 configuration file log4j2.xml
with preference is used from the following locations if the file is present:
Windows | Unix | |
---|---|---|
Controller | C:\ProgramData\sos-berlin.com\js7\controller\var\config\log42j.xml | /var/sos-berlin.com/js7/controller/var/config/log4j2,xml |
Agent | C:\ProgramData\sos-berlin.com\js7\agent\var_<port>\config\log42j.xml | /var/sos-berlin.com/js7/agent/var_<port>/config/log4j2,xml |
JOC Cockpit | C:\ProgramData\sos-berlin.com\js7\joc\jetty_base\resources\joc\log42j.xml | /var/sos-berlin.com/js7/joc/jetty_base/resources/joc/log4j2,xml |
Note:
- Preferably the above locations are used if changes to the log4j2.xml file are required. Installation of newer releases of JS7 components will not overwrite this from if present with the above locations.
- Changes to the Log4j2 configuration are applied within 60s and do not require the JS7 component to be restarted.