Page History

...

• 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 readable and 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 If you want to start the JobScheduler Windows service with the -env option or to reinstall a Windows Servicethen a reinstall is required (see below).

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

 ...
 # unix 
 export hello="world"
 export PERL5LIB=`perl -e 'print join ":", @INC'`
 export TMP="${SCHEDULER_DATA}/tmp"
 ...

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

...

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

Further references

Job and Order Parameters

• How to pass parameters to subsequent shell jobs in a job chain

...