Working with Job Servers
For information on creating Job Servers, see Creating a Job Server.
For information on deleting a Job Server, see Deleting a Job Server.
Overriding Job Server Default Values
You can override Job Server Parameter default values globally by setting the following registry entry:
/configuration/ProcessServerParameters/<name>
The <name> is the name of the Job Server Parameter. Note that this registry entry only affects default values; if you add the Job Server Parameter to the Job Server, then that value will have precedence over the value of this registry entry.
Only the scheduler-isolation-administrator can create/edit these registry entries.
Retrieving Support Files
When you use the action Get Support Files a process is prepared so you can choose which log files to retrieve. You select the files you are interested in and submit the process.
A new tab will open once the process has completed with the output of the process, choose <ID> stdout.log and a second tab will open with a link to the Job Job, from there you can access the zip file with all the logs.
Starting and Stopping Job Server Services
When you start a Job Server, all of its Services start automatically. When you stop a Job Server, all of its Services stop automatically. You can also start and stop Services independently.
Changing Job Server Parameters
If you need to make changes to Job Server Parameters, be aware that the updated Parameters will not take effect until the Job Server is restarted.
Worker Queues
By default, a Job Server has 100 worker Queues, which means that it can execute 100 concurrent Jobs. You can set the maximum number of worker Queues using the registry, as follows:
/configuration/requestQueueSize/<process_server_partition>/<process_server>/<service>
For example, to set the maximum workers for the ScriptService (RedwoodScript) to 20 for the Job Server named PS_TEST in the GLOBAL Partition, you would set this registry key:
/configuration/requestQueueSize/GLOBAL/PS_TEST/ScriptService=20
Forcing a Job to Run on a Specific Job Server
You can force a Job to run on a specific Job Server by using the <job>.setForcedProcessServer(<process_server>) RedwoodScript method. This is used in Pre Running actions and triggers, for example, to force a Job Call in a Workflow to run on the same host as another Job Call in the Workflow. You can recognize Job Calls that have been forced to run on a given Job Server in the Monitor screen by the Forced Job Server property, which is set to the name of the Job Server.
Errors and Operator Messages
Job Servers raise Operator Messages for warnings and errors under Configure > Control > Operator Messages. Check this screen if a Job Server appears to be behaving incorrectly or does not start.
Note: In an on-premises instance of RunMyJobs, if the connection is interrupted, the Job Server will attempt to reconnect to the Platform Agent. Meanwhile, Jobs on the Platform Agent will continue to run, but RunMyJobs will not be able to set them to their final status until the connection is restored. However, in an SaaS instance of RunMyJobs, if the connection is interrupted, the Platform Agent will attempt to reestablish contact with the Job Server.
Most settings for a Platform Agent are stored in the RunMyJobs repository as Job Server Parameters. However, settings that control what the Platform Agent can do on the computer where it runs must be configured on that computer.
The Platform Agent logs its operation status records to a file. For more information, see Platform Agent Logging.
Security Tab
The privileges available in the Security tab are as follows. For more information, see Security Tab.
| Privilege | Description |
|---|---|
| ProcessServer.Create | Create Job Servers |
| ProcessServer.Delete | Delete Job Servers |
| ProcessServer.Edit | Edit Job Servers |
| ProcessServer.View | Access Job Servers |
| ProcessServer.ViewJobs | View the processes in the Job Server |
| ProcessServer.Control | Open and close the Job Server |
| ProcessServer.UseForFileEvents | Use the Job Server for File Event processes |
| ProcessServer.SubmitOnto | Submit Jobs to the Jobs Server |