Page History

...

• 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).

...

• 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 an environment variable:

...