Using Command Line Options
- The command line option
-env=[adds an environment variable to the JobScheduler.
- This variable only exists in the scope of the JobScheduler.
- If a variable [
already exists in the user environment then the value of the ]
-envoption 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 an environment variable:
Environment Variables Script: jobscheduler_environment_variables.(sh|cmd)
The JobScheduler 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 readable and executable.
- Edit ./user_bin/jobscheduler_environment_variables.(sh|cmd) if you always want to start the JobScheduler with additional environment variables. If you want to start the JobScheduler Windows service with the
-envoption then a reinstall is required (see below).
Example snippet of /user_bin/jobscheduler_environment_variables.(sh|cmd) for adding an environment variable:
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.
- stop the JobScheduler if it is running:
- remove the JobScheduler service:
- install the JobScheduler service with
-envoption or edit the jobscheduler_environment_variables.cmd file as stated above
- start the JobScheduler service: