...
The role(s) JobScheduler is started with is/are determined by the -roles start option.
For example:
| No Formatcode |
|---|
scheduler.sh start -roleh1. roles=agent scheduler.sh start -rolesagentroles=agent,scheduler |
If the -roles option is not specified then JobScheduler will start with both roles.
This corresponds with the behaviour of versions before 1.7.
...
For the scheduler role the license key must contain the product key 7 in the license key:
| No Formatcode |
|---|
[licence] key1 h1. = SOS-DEMO-1-L54-4-7-??????? |
For the agent role the license key must contain the product key 22 in the license key:
| No Formatcode |
|---|
[licence] key1 = SOS-DEMO-1-L54-4-22-??????? |
...
In this role JobScheduler works as a "full" job scheduler. It can control processes itself but cannot execute processes that have been started by another JobScheduler.
In this role JobScheduler must be connected to a database (Version 1.7 onwards).
The following error message will be generated if the database configuration is not specified:
| No Formatcode |
|---|
SCHEDULER-205 No database given (entry db= in factory.ini) |
See the JobScheduler Messages list (Link does not work in IE) for the messages produced when other database problems occur.
...
In this role JobScheduler can only execute processes that have been started by another JobScheduler(remote scheduling).
It does not have its own configuration.
In this role JobScheduler does not require a database.
Any database configuration specified will be ignored.
...