...

Specify Java Options for a Controller or Agent

Unix Operating Systems

For Unix, the JAVA_OPTIONS environment variable can be set before running the Controller or Agent start script like this:

• From the Unix command line or from the Controller instance start script controller_<instance>.sh:

  Code Block
  language bash title Unix example to run the Controller start script with Java options
  # Set Java options before running the Controller start script export JAVA_OPTIONS="-Xms128m -Xmx500m" ./controller.sh start # Alternatively set Java options when running the Controller start script ./controller.sh start --java-options="-Xms128m -Xmx500m" # For use with a Controller daemon add this line to the Controller instance start script controller_<instance>.sh export JAVA_OPTIONS="-Xms128m -Xmx500m"

• From the Unix command line or from the Agent instance start script agent_4445.sh (assuming that port 4445 is used for the Agent):

  Code Block
  language bash title Unix example to run the Agent start script with Java options
  # Set Java options before running the Agent start script export JAVA_OPTIONS="-Xms128m -Xmx500m" ./agent.sh start # Alternatively set Java options when running the Agent start script ./agent.sh start --java-options="-Xms128m -Xmx500m" # For use with an Agent daemon add this line to the Agent instance start script agent_<port>.sh export JAVA_OPTIONS="-Xms128m -Xmx500m"

• Alternatively the JAVA_OPTIONS environment variable can be set with
  • the profile (~/.bashrc, ~/.bash_profile etc.) of the run-time account used for Controller or Agent,
  • the JS7 - systemd Service Files for automated Startup / Shutdown with Unix Systems.

...

Specify Java Options for JOC Cockpit

Unix Operating Systems

For Unix the JAVA_OPTIONS environment variable can be set before running the Jetty start script like this:

...