Date: Thu, 28 Mar 2024 21:16:33 +0000 (UTC) Message-ID: <2004714708.11969.1711660593128@change.sos-berlin.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_11968_1045730362.1711660593128" ------=_Part_11968_1045730362.1711660593128 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
In a number of situations it is recommended or required to set Java opti= ons to specify the behavior of the JVM.
Java options are set individually= for the respective JS7 products, the Controller, Agent and JOC Cockpit.
The examples below use the -Xms128m -Xmx500m
Java options which are used to spe=
cify heap memory requirements.
Do not feel tempted to apply the values from the examples which are used= for explanation purposes only.
For Unix, the JAVA_OPTIONS
environment variable can be set =
before running the Controller or Agent start script as follows:
From the Unix command line or from the Controller instance start the=
controller_<instance>.sh
script:
# Set J= ava options before running the Controller start script export JAVA_OPTIONS=3D"-Xms128m -Xmx500m" ./controller.sh start # Alternatively set Java options when running the Controller start script ./controller.sh start --java-options=3D"-Xms128m -Xmx500m" # For use with a Controller daemon add this line to the Controller instance= start script controller_<instance>.sh export JAVA_OPTIONS=3D"-Xms128m -Xmx500m"
From the Unix command line or from the Agent instance agent_44=
45.sh
start script (assuming that port 4445
is use=
d for the Agent):
# Set J= ava options before running the Agent start script export JAVA_OPTIONS=3D"-Xms128m -Xmx500m" ./agent.sh start # Alternatively set Java options when running the Agent start script ./agent.sh start --java-options=3D"-Xms128m -Xmx500m" # For use with an Agent daemon add this line to the Agent instance start sc= ript agent_<port>.sh export JAVA_OPTIONS=3D"-Xms128m -Xmx500m"
JAVA_OPTIONS
environment variable can be=
set with:
~/.bashrc, ~/.bash_profile
etc.) of the run-time account used fo=
r Controller or Agent,
For Windows, the JAVA_OPTIONS
environment variable can be s=
et before running the Controller or Agent start script as follows:
From the Windows command line or from the Controller instance =
controller_<instance>.cmd
start script:
@rem Se= t Java options before running the Controller start script set JAVA_OPTIONS=3D"-Xms128m -Xmx500m" .\controller.cmd start @rem Alternatively set Java options when running the Controller start scrip= t .\controller.cmd start --java-options=3D"-Xms128m -Xmx500m" @rem For use with a Controller Windows Service add this line to the Control= ler instance start script controller_<instance>.cmd set JAVA_OPTIONS=3D"-Xms128m" "-Xmx500m"
From the Windows command line or from the Agent instance agent=
_4445.cmd
start script (assuming that port 4445
is=
used for the Agent):
@rem Se= t Java options before running the Agent start script from the command line set JAVA_OPTIONS=3D"-Xms128m -Xmx500m" .\agent.cmd start @rem Alternatively set Java options when running the Agent start script .\agent.cmd start --java-options=3D"-Xms128m -Xmx500m" @rem For use with an Agent Windows Service add this line to the Agent insta= nce start script agent_<port>.cmd set JAVA_OPTIONS=3D"-Xms128m" "-Xmx500m"
\service
directory of the installation run<=
br>
js7_controller_<controller-id>w.=
exe
<controller-id>
corresponds to t=
he Controller ID the Controller has been installed with.C:\Program Files\sos-berlin.com\js7\controller\=
my-controller\service\js7_controller_mycontrollerw.exe
js7_agent_<port>w.exe
<port>
corresponds to the port t=
hat the Agent is operated with.C:\Program Files\sos-berlin.com\js7\agent_4445\=
service\js7_agent_4445w.exe
The examples below use the -Xms128m -Xmx500m
Java options that are used to=
specify heap memory requirements.
Do not feel tempted to apply the values from the examples below whi= ch are used for explanation purposes only.
For Unix the JAVA_OPTIONS
environment variable can be set b=
efore running the Jetty start script as follows:
The Jetty start script is available from the installation directory&=
nbsp; /opt/sos-berlin.com/js7/joc/jetty/bin/jetty.sh
or a=
location specified during installation:
# Set J= ava options before running the Jetty start script export JAVA_OPTIONS=3D"-Xms128m -Xmx500m" ./jetty.sh start
When running the JOC Cockpit as a daemon then the following li=
ne can be added to the $HOME/.jocrc
file of the JOC =
Cockpit run-time account. This file is created by the installer and it is u=
sed if it exists and is executable. The $HOME
directory is ide=
ntified from the /etc/passwd
file during installatio=
n.
export = JAVA_OPTIONS=3D"-Xms128m -Xmx500m"
JAVA_OPTIONS
environment variable can be=
set with:
~/.bashrc, ~/.bash_profile
etc.) of the run-time account used fo=
r JOC Cockpit,
For Windows, the JAVA_OPTIONS
environment variable can be s=
et before running the JOC Cockpit start script like this:
The C:\Program Files\sos-berlin.com\js7\joc\jetty\bin\jett=
y.cmd
start script is only available when the JOC Cockpit is not ins=
talled as a Windows Service.
@rem Se= t Java options before running the JOC Cockpit start script set JAVA_OPTIONS=3D"-Xms128m" "-Xmx500m" .\jetty.cmd start
\service
directory run:
js7_jocw.exe
C:\Program Files\sos-berlin.com\js7\joc\service=
\js7_jocw.exe