From the System Administration tool the JobServer Engine can be started and stopped. The status of JobServer can be accessed from here. The JobServer Engine can be started in two ways - Normal and Gradual. The JobServer Engine can be in three possible states:
Using this button will start JobServer in a normal fashion, moving it from "Idling" mode to "Running" mode. This means the Scheduler and any jobs in the Queue will be kicked off as soon as possible. Any job that is ready to run will run as soon as its corresponding Partition and Queue can accept it. If there is a startup failure of any kind, check the "Startup Log" for details. The "Startup Log" shows the detailed steps involved in starting up the JobServer Engine and can indicate reasons for startup failure. This GUI can be found under the "System Log" tab and will be shown at the bottom of the startup screen.
In this startup mode, the JobServer's Scheduler and Job Processing are suspended. This means JobServer will go through the normal startup process, except jobs will not get scheduled nor will any jobs get run. This startup mode is useful if the administrator wants to startup JobServer gradually, especially, when diagnosing problems. Later, JobServer can be fully activated/started, when the administrator is ready, by going to the "Engine Controls" tab and activating the "System Job Scheduling" (this allows the Scheduler to begin to look for jobs that are ready to run) and/or the "System Job Processing" (this allows Partitions to begin consuming jobs). If both these are activated, this puts JobServer into normal running condition, as if it where started using the normal startup option.
JobServer and all running jobs can be shutdown immediately. This means that the JobServer process will be terminated and any running jobs will terminated. When JobServer is restarted any terminated jobs will be marked as such. Note, this shutdown option should only be used if you can't wait for jobs to complete normally. Click the "Refresh" button to get updated as to when JobServer has completed the shutdown process.
As the name indicates, JobServer can be shutdown gracefully. With this shutdown mode, the JobServer process is not terminated until all jobs have completed their processing. No new jobs will be allowed to begin running once the JobServer enters this mode. Once all jobs have completed, the JobServer process itself will terminate. Click the "Refresh" button to get updated status as to when JobServer has completed the shutdown process.
If you have Mule enabled in our JobServer environment you may use this feature. When the JobServer scheduling engine is started (and jobs allowed to run), you can also start a Mule Server/Container allowing your JobServer instance to host/implement/run mule endpoint services. Checking the box will enable the Mule container to be started the next time the JobServer engine is started (or restarted if it is already running).
This link will allow you to see the JobServer Runtime Logs and Startup Logs. This is basically a short-cut to the JobServer logs found in the System Logs tab.