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. 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
- This log is used Windows and contains messages about the Windows Service start/stop.
- sos_joc-stdout.YYYY-MM-DD.log
- This log is used by the Procrun application used to start Jetty as a Windows Service.
- 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.
- 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.
- Install*.log
- The log output that is created by the installer.
- The log output that is created by the installer.