...
- Edit the
./bin/jobscheduler_agent_4445.sh
. Find the environment variables for the JobScheduler Universal Agent.
- All environment variables are commented out in the instance script, i.e. the default values are used.
If you want to set an environment variable then the line with the variable has to be uncommented.
SCHEDULER_HOME
This variable has to point to the installation path of the JobScheduler Universal Agent, e.g.
/opt/sos-berlin.com/jobscheduler_agent
.
If the instance script is exclusively used in the current./bin
directory then this variable can remain unused..Note This setting is required if the instance script is used as a service init script in
/ect/init.d
to find the Agent installation!SCHEDULER_USER
Specifies the user account that the JobScheduler Agent is operated for. This includes running jobs with the permissions of the specified user.
Without setting this environment variable the user account that runs the start script is used.Note This setting is required if the instance script is used as a service init script in
/ect/init.d
to avoid that the Agent runs with theroot
user!SCHEDULER_HTTP_PORT
The http port of the Agent. This has to be the same value as the suffix in the instance script basename. In this example
Code Block SCHEDULER_HTTP_PORT=4445
This option can be also used for indicating which network interfaces the JobScheduler Agent should listen to if you specify a hostname or ip address in addition.
Code Block SCHEDULER_HTTP_PORT=localhost:4445
SCHEDULER_HTTPS_PORT
The https port of the Agent.
Code Block SCHEDULER_HTTPHTTPS_PORT=40445
This option can be also used for indicating which network interfaces the JobScheduler Agent should listen to if you specify a hostname or ip address in addition.
Code Block SCHEDULER_HTTPHTTPS_PORT=123.456.789:40445
SCHEDULER_LOG_DIR
Set the directory where the JobScheduler Agent log files are created. The default location is
SCHEDULER_HOME/logs
.
It is recommended to use the same log directory for all instances. According to the Linux Filesystem Hierarchy Standard (FHS) you can use for exampleCode Block SCHEDULER_LOG_DIR=/var/log/jobscheduler/agent
Note Make sure that the
SCHEDULER_USER
has read and write permissions inSCHEDULER_LOG_DIR
.
If you use the sameSCHEDULER_LOG_DIR
for all instances then make sure that theSCHEDULER_USER
of all instances has read and write permissions.SCHEDULER_PID_FILE_DIR
Set the directory where the JobScheduler Agent pid file is created. The default location is
SCHEDULER_LOG_DIR.
Note Make sure that the
SCHEDULER_USER
has read and write permissions in
.SCHEDULER_PID_FILE_DIR
If you use the sameSCHEDULER_PID_FILE_DIR
for all instances then make sure that theSCHEDULER_USER
of all instances has read and write permissions.SCHEDULER_WORK_DIR
The default working directory of the JobScheduler Agent is
SCHEDULER_HOME
. You can specify a different working directory, e.g.$HOME
.- According to the shell in use you can set the environment variables except
SCHEDULER_HOME
,SCHEDULER_HTTP_PORT
andSCHEDULER_USER
in a~/.profile
or~/.bashrc
file too.
If you want to install a JobScheduler Agent service for an automated start-up and shutdown then copy this instance script to
/ect/init.d
or corresponding locations.Code Block language bash title create a service init script set automated start-up and shutdown > cp ./bin/jobscheduler_agent_4445.sh /etc/init.d/jobscheduler_agent_4445 > # on SuSe or CentOS > chkconfig jobscheduler_agent_4445 > # on Ubuntu or Debian > update-rc.d jobscheduler_agent_4445 default
...