Page History

...

The environment variables can be used for substitutions (see Job Scheduler Reference Documentation).

Startscript with -env

Sample for starting the Job Scheduler with the variable hellh1. world:

 unix-shell>[install_path]/bin/jobscheduler.sh start -env=hello=world 
 windows-shell>[install_path]\bin\jobscheduler.cmd start -env=hello=world 

Edit jobscheduler_environment_variables.(sh|cmd) file

If you always want to start the Job Scheduler with additional environment variables then you can edit the SCHEDULER_PARAMS variable in the install_path/bin/jobscheduler_environment_variables.(sh|cmd) file. Then it is not necessary to call the above startscript with the -env option.

...

 ...
 # unix sample
 SCHEDULER_PARAMS="... \"-env=hello=world\" ..."
 ...
 rem windows sample
 set SCHEDULER_PARAMS=... -env="hello=world" ...
 ...

Windows Service

A windows service starts the Job Scheduler always with that options which it is installed. After the windows Job Scheduler setup a service is already installed so that you must reinstall the service to add an environment variable.

...