Java options in JobScheduler Universal Agent start script

Current Situation

• With Java 1.8 the initial memory allocation has changed, for details see How to manage the Java heap space
• As a result on start-up of the Universal Agent an excessive amount of virtual memory is assigned by Java.
• The start script jobscheduler_agent.sh makes use of the environment variable JAVA_OPTIONS that allows to apply memory settings such as -Xms100m, however this is poorly documented and requires to be set before installing the Agent.

Desired Behavior

• Add a command line option -java-options to the Universal Agent start script jobscheduler_agent.sh to set the JAVA_OPTIONS from the command line.
• Update the documentation in tne JobScheduler Universal Agent - Installation & Operation page to state the use of the -java-options setting:
  • Recommend use: the Agent should not require more than 100 MB virtual memory, i.e. -Xms100m
  • Add a link to the before-mentioned knowledge base article.

Delimitation

• Tasks started by the Universal Agent are exposed to the same initial memory allocation that is applied by Java. To manage memory consumption for jobs that are executed on Agents the setting <job java_options="..."> is applied by the Agent when starting the task.