Page History
...
- Log file location:
logs
sub-directory of the JOC Cockpit installation. - Jetty Log
- Log file:
jetty.log
- Purpose: log output created on start-up of the servlet container. If the Jetty servlet container wouldn't start then this is the log file to check for errors.
- Log file:
- JOC Cockpit Log
- Main log file:
joc.log
- Debug log file:
joc-debug.log
- Purpose: log output created by the JOC Cockpit application. For problems occurring during operation of JOC Cockpit, e.g. with database connections, this log file includes detailed information.
- Main log file:
- Audit Log
- Log file:
audit.log
- Purpose: The JS7 - Audit Log stores information about any changes to the state of objects, such as deploying workflows, cancelling and suspending orders etc. Consider that information from the audit log file can be subject to compliance requirements.
- Log file:
- Service Logs
- JS7 - Cleanup Service
- Main log file:
service-cleanup.log
- Debug log file:
service-cleanup-debug.log
- Purpose: cleanup entries from the order and task history, deployment history and , daily plan history and audit log.
- Main log file:
- JS7 - Cluster Service
- Main log file:
service-cluster.log
- Debug log file:
service-cluster-debug.log
- Purpose: operate the JOC Cockpit cluster and perform switch-over and fail-over operations when required.
- Main log file:
- JS7 - Daily Plan Service
- Main log file:
service-dailyplan.log
- Debug log file:
service-dailyplan-debug.log
- Purpose: plan orders from schedules and submit orders to Controllers.
- Main log file:
- JS7 - History Service
- Main log file:
service-history.log
- Debug log file:
service-history-debug.log
- Purpose: receive events about order state transitions and log output of underlying jobs from Controllers and add them to the history.
- Main log file:
- JS7 - Cleanup Service
...
Overview
Content Tools