...
-http-port=<[hostname or ip address:]number>
- is the HTTP port that the Agent is listening to in order to receive requests from a JobScheduler Master:
jobscheduler_agent.cmd|sh command -http-port=####
- where
####
is the numeric port. - 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
- Without this option being used the port defaults to 4445 and the JobScheduler Agent listens to all available network interfaces.
- Should you want to specify a port then the following precedence applies:
- First precedence: command line option
- Second precedence: environment variable
SCHEDULER_HTTP_PORT
(see below) - Third precedence: use of default value
- is the HTTP port that the Agent is listening to in order to receive requests from a JobScheduler Master:
-https-port=<
[hostname or ip address:]
number>- is the HTTPS port that the Agent is listening to in order to receive requests from a JobScheduler Master:
jobscheduler_agent.cmd|sh command -https-port=####
- where
####
is the numeric port. - 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
- Without this option being used the port defaults to 4445and the JobScheduler Agent listens to all available network interfaces.
- Should you want to specify a port then the following precedence applies:
- First precedence: command line option
- Second precedence: environment variable
SCHEDULER_HTTP_PORT
(see below) - Third precedence: use of default value
- is the HTTPS port that the Agent is listening to in order to receive requests from a JobScheduler Master:
=<number>-data-directory
- Location of the data directory.
- It has to be unique over all JobScheduler Universal Agent instances
- Should you want to specify a data directory then the following precedence applies:
- First precedence: command line option
- Second precedence: environment variable
SCHEDULER_DATA
(see below) - Third precedence: use of default value (=
SCHEDULER_HOME/var_SCHEDULER_HTTP_PORT
)
-timeout=<number>
- This option can be used to specify the number of seconds that the Agent will wait for tasks to stop.
- This option can be applied for
stop
andrestart
commands. - The Agent sends a SIGTERM signal to the taksk and having reached the timeout a SIGKILL signal will be sent to stop any tasks immediately.
=<location of kill script>-kill-script
The kill scripts provide the functionality to kill a task and it's child processes.
- Two kill scripts are provided
./bin/jobscheduler_agent_kill_task.sh
for Unix as default.\bin\jobscheduler_agent_kill_task.cmd
for Windows as default
This option can be used to specify the location of a different "kill script" if necessary
Should you want to specify a different "kill script" then the following precedence applies:
- First precedence: command line option
- Second precedence: environment variable
SCHEDULER_KILL_SCRIPT
(see below) - Third precedence: use of default value
=<java options>-java-options
With Java 1.8 the initial memory allocation has changed, for details see How to manage the Java heap space.
This option can be used to apply Java options for the JobScheduler Universal Agent, e.g. the memory settings.
Without this option being used the Java options default to '-Xms100m'.
Should you want to specify the Java options then the following precedence applies:
- First precedence: command line option
- Second precedence: environment variable
JAVA_OPTIONS
(see below) - Third precedence: use of default value
java-options=<java options>-job-
Without this option being used the Java options for each job which is started by the JobScheduler Universal Agent.
Should you want to specify the Java options for the jobs then the following precedence applies:
- First precedence: command line option
- Second precedence: environment variable
SCHEDULER_JOB_JAVA_OPTIONS
(see below)
...