Page History

h1. How can I add environment variables to JobScheduler?

...

Using Command Line Options

• The command line option -env=var_name=var_value adds an environment variable to the JobScheduler.
  • This variable is established only 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).

...

Start Script with -env

Example for starting the JobScheduler with the an environment 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"

...

Environment Variables Script: jobscheduler_environment_variables.(sh|cmd)

...

The JobScheduler startscript start script reads the environment from the .\user_bin\jobscheduler_environment_variables.(sh|cmd) script.

• You will find an example in ./user_bin/jobscheduler_environment_variables.(sh|cmd)-example.
• Rename this file to ./user_bin/jobscheduler_environment_variables.(sh|cmd) to make it effective.

...

• For Unix make sure that ./user_bin/jobscheduler_environment_variables.sh is executable.
• Edit ./user_bin/jobscheduler_environment_variables.(sh|cmd) if you always want to start the JobScheduler with additional environment variables.

...

•  Then it

...

• would not be necessary to call the above

...

• start script with the -env option or to reinstall a Windows Service.

Example snippet of install_path/user_bin/jobscheduler_environment_variables.(sh|cmd) for adding the an environment variable helloworld:

Code Block
... # unix export hello="world" export PERL5LIB=`perl -e 'print join ":", @INC'` ...

Code Block
... rem windows SET SCHEDULER_PARAMS=%SCHEDULER_PARAMS% -env="hello=world" SET SCHEDULER_START_PARAMS=%SCHEDULER_START_PARAMS% -env="hello=world" ...

Windows Service

A The Windows service Service always starts JobScheduler with the options which are installed. After and environment variables that have been used for installation. During the Windows JobScheduler setup a service Windows Service is already installed so that it must be reinstalled with additional has to be re-installed in order to make new environment variables effective.

For this ...

• stop the JobScheduler if necessaryit were started:
   

 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 like 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