Scope

• JS7 provides a number of log files for Controller, Agent and JOC Cockpit.
• The purpose of log files and their location are explained.

Controller

• Main Log
  • Log file: controller.log
  • Location: logs sub-directory of the Controller installation.

Agent

• Main Log
  • Log file: agent.log
  • Location: logs sub-directory of the Agent installation.

JOC Cockpit

• Location: logs sub-directory of the JOC Cockpit installation.
• Jetty Log
  • Log file: jetty-yyyy-mm-dd.log
    • Consider that yyyy-mm-dd is replaced by the respective date that the Jetty servlet container was started.
  • 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. 
• JOC Cockpit Log
  • Log file: joc.log
  • Purpose: Log output created by the JOC Cockpit application. For problems occurring during operation of JOC Cockpit, e.g. use of database connections, this log file includes detailed information.
• Service Logs
  • Cleanup Service
    • Log file: service-cleanup.log
    • Purpose: cleanup entries from the order and task history, deployment history and daily plan history. 
  • Cluster Service
    • Log file: service-cluster.log
    • Purpose: operate the JOC Cockpit cluster and perform switch-over and fail-over operations when required.
  • Daily Plan Service
    • Log file: service-dailyplan.log
    • Purpose: plan orders from schedules and submit orders to Controllers
  • History Service
    • Log file: service-history.log
    • Purpose: Receive events about order state transitions and log output of underlying jobs from a Controller and add them to the history.