Page History

...

• The command line option -env=[var_name]=[var_value] adds an environment variable to the JobScheduler.
  • This variable is established  only exists in the scope of the JobScheduler.
• If a variable [var_name] already exists in the user environment then the value of the -env option will become effective.
• The Windows Service of the JobScheduler reads the system and user environment only if it runs in the corresponding user account.
• Environment variables are considered for substitution when used in settings (see Job Scheduler Reference Documentation).

...

The Windows Service always starts JobScheduler with the options and environment variables that have been used for installation. During the Windows JobScheduler setup a Windows Service is installed that has to be re-installed in order to make new environment variables effective.

For this:

• stop the JobScheduler if it were startedis running:
   

 windows-shell>[install_path]\bin\jobscheduler.cmd stop

• remove the JobScheduler service: 

 windows-shell>[install_path]\bin\jobscheduler.cmd remove

• install the JobScheduler service with -env option or edit the jobscheduler_environment_variables.cmd file as stated above 

 windows-shell>[install_path]\bin\jobscheduler.cmd install -env=hello=world
 ...or...
 windows-shell>[install_path]\bin\jobscheduler.cmd install
 

• start the JobScheduler service:
   

 windows-shell>[install_path]\bin\jobscheduler.cmd start_service

...