Open JobScheduler Operations Center (JOC) Cockpit
The JOC Cockpit is a GUI for monitoring and operating the JobScheduler. FEATURE AVAILABILITY STARTING FROM RELEASE 1.11
You open the JOC Cockpit in a browser (Firefox, Microsoft® Edge® and Chrome are supported) with the following URL:
http://[joc_host]:[joc_http_port]
where the joc_http_port was set in the Network Configuration part of the Installation procedure.
See the JOC Cockpit - Installation article for further information about logging into the JOC Cockpit for the first time.
Note that when you open the JOC Cockpit from another computer, you must make sure that the communication is not blocked by a firewall.
If you have updated the JobScheduler installation, it will be necessary to clear the browser cache and to refresh the browser with Ctrl
& F5
for the changes to fully take effect.
The JOC Cockpit can also be called using HTTPS when suitably configured. See the JOC Cockpit - HTTPS Authentication article for further information.
Open JobScheduler Operations Center (JOC)
The Classic JOC user interface is entering retirement:
FEATURE AVAILABILITY ENDING WITH RELEASE 1.11
The JOC Cockpit user interface replaces JOC:
FEATURE AVAILABILITY STARTING FROM RELEASE 1.11
See the JOC Cockpit Article for more information about the JOC Cockpit.JobScheduler Operations Center (JOC) is a GUI for monitoring and operating the JobScheduler.
You open JOC in a browser (Firefox, Microsoft Internet Explorer® and Chrome are supported) with the following URL:
Until JobScheduler version 1.10.x you can also open JOC with the following URLs.
http://[scheduler_host]:[jobscheduler_http_port]/
https://[scheduler_host]:[jobscheduler_https_port]/
In all three cases the jobscheduler_http_port or jobscheduler_https_port were set in the Network Configuration part of the Installation procedure.
When you open JOC from another computer, you must make sure that the communication is not blocked by a firewall or by the Security setting of the JobScheduler.
If you have updated the JobScheduler installation, it may be necessary to clear the browser cache for the changes to take effect in JOC.
Open JobScheduler Object Editor (JOE)
JOE, the JobScheduler Object Editor is an application for creating, editing and maintaining the JobScheduler objects (jobs, job chains, orders, schedules, etc).
You start JOE with ...
$SCHEDULER_HOME\bin\jobeditor.cmd
$SCHEDULER_HOME/bin/jobeditor.sh
An X-Server and GTK2 is necessary on Unix® systems. The necessary libraries must be installed with the same number of bits as JOE.
Troubleshooting
Should you have problems when you start JOE on Microsoft Windows®, you can add debug
as an argument your call to see the error.
$SCHEDULER_HOME\bin\jobeditor.cmd debug
For example, you have to adjust the environment variable $JAVA_HOME
in the $SCHEDULER_HOME/user_bin/jobeditor_environment_variables
file if you get the following error after starting JOE:
Cannot load 32-bit SWT libraries on 64-bit Java® Virtual Machine (JVM)
See the JobScheduler Master Installation - 07 - Manual Configuration article for more information.
Open JobScheduler Information Dashboard (JID)
The JID Dashboard is entering retirement:
FEATURE AVAILABILITY ENDING WITH RELEASE 1.11
The JOC Cockpit user interface is a replacement for JID:
FEATURE AVAILABILITY STARTING FROM RELEASE 1.11
JobScheduler Information Dashboard (JID) is an application to provide an overview of the jobs planned and those that have successfully been completed.
See also the Dashboard documentation for more details.
You start JID using ...
$SCHEDULER_HOME\bin\dashboard.cmd
$SCHEDULER_HOME/bin/dashboard.sh
An X-Server and GTK2 is necessary on Unix® systems. The necessary libraries must be installed with the same number of bits as JID.
Troubleshooting
Should you have problems when you start JID on Microsoft Windows®, you can add debug
as an argument your call to see the error.
$SCHEDULER_HOME\bin\jobeditor.cmd debug
For example when you get the error:
Cannot load 32-bit SWT libraries on 64-bit Java® Virtual Machine (JVM)
after starting JOE you have to adjust the environment variable $JAVA_HOME
in the $SCHEDULER_HOME/user_bin/jobeditor_environment_variables
file.
See the JobScheduler Master Installation - 07 - Manual Configuration article for more information.