- The History View includes a number of sub-views to display the:
- JS7 - Order History for the execution of orders passing workflow workflows and jobs,
- JS7 - Task History for the execution of tasks and respective their log output,
- JS7 - File Transfer History for details about transfers performed with the YADE Add-on,
- JS7 - Deployment History with information about objects such as workflows deployed to a Controller,
- JS7 - Daily Plan History for details about submissions submission of orders for the respective a particular Daily Plan date.
- The JS7 History works asynchronously:
- Events about JS7 - Order State Transitions can occur with the Agent and with the Controller.
- Such events are subscribed to by the JS7 - History Service background task.
- Events include state transitions and log output of jobs that are added to the JS7 - Database and are available with the History View.
- The History Service works independently from user interaction and displays added or updated history items on-the-fly for all users connected to an active JOC Cockpit instance.
- Any All sub-views of the History View offer to export allow history items to be exported as files in Excel® format.
- In case of outage of the Primary Controller instance the History Service will automatically switch to the Secondary Controller instance to retrieve history items. Fail-over typically takes place within 10s.
- In case of outage of the History Service the Controller will store events with its journal until the History Service is up again and will acknowledge receipt of events. Only then will events are be released from a the Controller's journal. Consider Note that the Controller journal can grow in case of during longer outages of the History Service if a larger number of jobs and/or abundant log output of jobs have to be handled by the Controller. Therefore a Controller should be assigned sufficient storage to hold its journal for the maximum expected duration of an outage of JOC Cockpit, see JS7 - Sizing.
- The History Service will resume operation after an outage and will continue to receive events from a Controller and to write events to the database.