Skip to end of metadata
Go to start of metadata

Important: The concept described on this page only applies for JobScheduler Version 1.7+

Starting JobScheduler

JobScheduler can be started with one or both of the following roles:

  • scheduler
  • agent

The role(s) JobScheduler is started with determines aspects of its behaviour and whether or not it requires a database.

The role(s) JobScheduler is started with is/are determined by the -roles start option.
For example:

If the -roles option is not specified then JobScheduler will start with both roles.
This corresponds with the behaviour of versions before 1.7.

Starting JobScheduler with both roles means that a database connection must exist. From version 1.7 onwards, operation of JobScheduler without a database is only possible when it is started with only the agent role.

Checking the license key

A further precondition for the use of a role is that an appropriate license key is specified in the sos.ini file.

For the scheduler role the license key must contain the product key 7 in the license key:

For the agent role the license key must contain the product key 22 in the license key:

 

The "scheduler" role

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:

See the JobScheduler Messages list (Link does not work in IE) for the messages produced when other database problems occur.

The "agent" role

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.

See also

For further information see: