Page History

...

• The lower part of the screenshot displays the Order History that makes the order log available when clicking the Order ID.
• Right to the Order History users find the Task History that displays individual tasks running executed for the given workflow. Clicking the job name will display the task logTask Log.
• Both logs are similarly available from the JS7 - Order History and JS7 - Task History.
• The size of the workflow's Order History and Task History can be changed in JS7 - Profiles - Preferences.

...

• The top of the screen offers a number of options:
  • and will expand and collapse log output of any jobs executed for the workflow.
  • and will expand and collapse output of the selected job.
  • Main: displays/hides lines holding information start times, job names etc. that are using the [MAIN] qualifier.
  • Success: displays/hides lines holding success messages using the [SUCCESS] qualifier. Such lines use the green color.
  • stdout: displays/hides log output from jobs written to the stdout channel.
  • Debug: displays/hides log output from JVM jobs writing debug messages, see JS7 - Job Classes.
  • Detail: displays/hides details about events, for example the timestamp when an order forks is forking and when child orders joinare joining. Such lines use the blue color.
• On the right side of the screen users find the icon that opens the right navigation panel:
  • The panel displays jobs and other JS7 - Workflow Instructions in historical sequence.
    • If a job fails and is repeated then it will occur a number of times of times.
    • The navigation panel displays the hierarchy of workflow instructions.
  • and will expand and collapse the navigation panel for nested workflow instructions.
  • Clicking a specific job or instruction in the navigation panel will highlight the log output related to the instruction.

...

• Log output is created
  • from jobs that write to the stdout or stderr channels,
  • from events that signal processing of instructions such as a job start, forking / joining of an order etc.
• Log output is displayed in historic sequence. If jobs are repeated then related log output is made available.
• If jobs are running on Agents that make use of different time zones, then users can specify timestamps in log output to be converted to their time zone, see JS7 - Profiles - Preferences. Otherwise the original timestamps of the Agent processing the job or instruction will be displayed.

...

• unavailability of the Controller. In this situation the Agent will store log output to its journal and will try to stream log output later on when a Connection is established by the Controller.
• unavailability of JOC Cockpit. In this situation the Controller will store log output to its journal and will try to stream log output later on when a Connection is established by JOC Cockpit.
• high load of the database.

Completion of Logs

Task Logs are completed when the task is tasks are terminated. At that point in time the task log is persisted to the database by the History Service running in JOC Cockpit. Before completion log output of tasks is stored to temporary files in the JOC Cockpit's <JETTY_BASE>/logs/history directory.

Cluster Operation

This includes that the active JOC Cockpit instance in a cluster will receive log output only. When using a standby JOC Cockpit instance in a cluster then no Running Log is available., Instead, logs become available after completion of orders and tasks.

...