JOC Cockpit - Logging

Log Files

The JobScheduler Web Services provide extensive logging for the JOC Cockpit, including the compliance-conform Audit Log.The JOC Cockpit uses the following log files:

• YYYY_MM_DD.stderrout.log
  
  • This log rotates per restart of the JOC Cockpit and per day. It shows startup messages and error messages. This file should not grow in a considerable way as it used mainly for error messages.
• sos_joc-stderr.YYYY-MM-DD.log and sos_joc-stdout.YYYY-MM-DD.log
  
  •  This log is used on Windows systems and contains messages about the Windows Service start/stop.
• start.log
  • This log is used on Linux systems.
•  JOCAuditLog.log
  • This file includes the same information that is visible in the JOC Cockpit from the Audit Log View. All interventions that modify the status of jobs, job chains and orders are written to this file.
    
  • This file is important for compliance purposes. Therefore it is not rotated.
  • Growth should not be harmful as one line of log output is created per user action.
•  Install*.log
  
  • The log output that is created by the installer.
    

Log File Location

All JOC Cockpit log files are saved in a common logs folder.

If the Jetty Web Server provided with the JOC Cockpit installation is installed in its default location then the JOC Cockpit log files will be found in the jetty_base directory. The default paths to this directory are:

• /home/[user]/sos-berlin.com/joc on Linux systems and

• C:\ProgramData\sos-berlin.com\joc on Windows.

For more information see the Jetty Installation & Configuration section of the JOC Cockpit - Installation article.

Logging Configuration

Logging for the JOC Cockpit is configured in a log4j.properties file, which can be found in the jetty_base/resources/joc directory.

Note that the log4j.properties file is overwritten during installation so system administrators wishing to change, for example, the location or name of the Audit Log file, will need to take suitable precautions whilst updating the JOC Cockpit.