WORK IN PROGRESS
JobScheduler Operations Center
The JobScheduler Operations Center (JOC) is used to monitor and control the jobs, job chains and orders.
You open JOC in a browser with the URL:
where scheduler_host and scheduler_port are the hostname and the TCP port number of the JobScheduler.
Overview Communication Between JOC and JobScheduler Engine
Factors affects JOC Performance
Size of data packet
- One of major factor affecting data packet sent back by JobScheduler depend upon number JobScheduler objects e.g. job chain, job, order, deployed in live folder.
- Number of running jobs/tasks
- Number of running jobs/tasks also add addition run time information e.g. start time, end time, step text etc.
- Number of history entries per order/task
- In JOC user can configure how many order/task histories he want to see. As number of order/task history is higher, JobScheduler engine needs more time to fetch that information from database. Also the data packet size will be bigger.
- Auto update frequency
- By default auto update of JOC is disabled . But if user enable the Auto update
- Database and Network performance
JOC Performance Debugging
The JOC offers a feature to see in real time time taken by JobScheduler to prepare the data packet and transportation time to JOC. Also user can see rendering time required by JOC for different sections of the JOC GUI.
Enable Debugging
Disable Debugging
Analyze Data In Debug Log
JOC Performance improvement