Date: Fri, 29 Mar 2024 08:22:53 +0000 (UTC) Message-ID: <468553723.12611.1711700573435@change.sos-berlin.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_12610_169159374.1711700573435" ------=_Part_12610_169159374.1711700573435 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
-env=3D[var_name]=
code>=3D[var_value]
adds an environment variable to the JobScheduler.
- This variable only exists in the scope of the JobScheduler.
var_name]=
code> already exists in the user environment then the value of the -e=
nv
option will become effective.
Example for starting the JobScheduler with an environment variable:
unix-sh= ell>[install_path]/bin/jobscheduler.sh start -env=3D"hello=3Dworld"=20 windows-shell>[install_path]\bin\jobscheduler.cmd start -env=3D"hello= =3Dworld"
The JobScheduler start script reads the environment from the .\user_= bin\jobscheduler_environment_variables.(sh|cmd) script.
-env
option the=
n a reinstall is required (see below).Example snippet of [install_path]/user_bin/jobscheduler_environment_variables.(sh|cmd) for adding a= n environment variable:
... # unix=20 export hello=3D"world" export PERL5LIB=3D`perl -e 'print join ":", @INC'` export TMP=3D"${SCHEDULER_DATA}/tmp" ...
... rem windows=20 SET SCHEDULER_PARAMS=3D%SCHEDULER_PARAMS% -env=3D"hello=3Dworld"=20 SET SCHEDULER_START_PARAMS=3D%SCHEDULER_START_PARAMS% -env=3D"hello=3Dworl= d" ...
The Windows Service always starts JobScheduler with the options and envi= ronment variables that have been used for installation. During the Windows = JobScheduler setup a Windows Service is installed that has to be re-install= ed in order to make new environment variables effective.
For this:
windows= -shell>[install_path]\bin\jobscheduler.cmd stop
windows= -shell>[install_path]\bin\jobscheduler.cmd remove
-env
option or edit =
the jobscheduler_environment_variables.cmd file as stated above
windows= -shell>[install_path]\bin\jobscheduler.cmd install -env=3Dhello=3Dworld ...or... windows-shell>[install_path]\bin\jobscheduler.cmd install
windows= -shell>[install_path]\bin\jobscheduler.cmd start_service