Tuning Your JVM

Web Engagement Server allows you to tune your JVM parameters, which is especially important with respect to the virtual memory allocated to the JVM. You can modify your JVM parameters in the "'launcher.ini'" or setenv.sh file that is located at Web Engagement installation directory\server\.

Tuning Your Memory Allocation

Windows

The out-of-box memory settings for the launcher.ini file are as follows:

[JavaArgs]
-Xmx4096m
-Xms4096m

Linux

The out-of-box memory settings for the setenv.sh file are as follows:

MEMORY_MIN=4096m
MEMORY_MAX=4096m

If you want to change these settings, update the appropriate values and restart the Web Engagement Server.

Enabling the JMX Port

You can monitor the JVM where your Web Engagement Server is running by using some of the standard Java tools distributed with the JDK, such as JConsole or Visual VM. Since these tools work through the JMX port, the Web Engagement Server needs to open this port on startup.

Windows

The launcher.ini file contains all of the settings you need to turn on JMX access:

; uncomment and configure the properties below to use JMX
;-Dcom.sun.management.jmxremote.local.only=false 
;-Dcom.sun.management.jmxremote.port=5999
;-Dcom.sun.management.jmxremote.authenticate=false
;-Dcom.sun.management.jmxremote.ssl=false

Linux

The setenv.sh file contains all of the settings you need to turn on JMX access:

# Uncomment for enabling JMX Remote
#JMX_PORT=5999
#JAVA_OPTS="${JAVA_OPTS} \
#  -Dcom.sun.management.jmxremote.port=${JMX_PORT} \
#  -Dcom.sun.management.jmxremote.local.only=false \
#  -Dcom.sun.management.jmxremote.ssl=false \
#  -Dcom.sun.management.jmxremote.authenticate=false"

As you can see, the JMX parameters are turned off by default. To enable JMX access, you need to uncomment these settings.

Note: Opening the JMX port without adequate security can be risky. See the JMX monitoring and management documentation for information about how to tune your security settings when using JMX to monitor your JVM.