Wrapper Configuration

Related file: wrapper.conf

Thewrapper.conf configuration file contains the settings for the wrapper process used to start, stop and restart the xServer.
Most settings do not have to be changed. In fact, modifications of settings other than those described below may lead to unpredictable behavior.
Please refer to the tanuki software wrapper configuration documentation for more information before you modify these settings.

Default Environment Settings

Thewrapper.conf configuration file contains default settings for environment variables. If necessary, the default settings may be changed in the wrapper.conf or set as an environment variable before the wrapper process is started.


        #*****************************
        # Default environment settings
        #***************************** 
        set.default.XSERVER2_JAVA_HOME=%JAVA_HOME%
        set.default.XSERVER2_LOG_DIRECTORY=./logs

Memory Settings

The wrapper sets the memory for the web server JVM using default Java parameters -Xmx and -Xms. You can change these memory settings in the wrapper configuration file depending on your usage profile. If you use large messages with a high level of concurrency you may want to increase the defaults for productive use.

A good rule of thumb is poolsize × maximum expected response size in mega bytes × 2.

# Initial Java Heap Size (in MB)
wrapper.java.initmemory=512

# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=512

Management Console Activation

To disable the administrative PTV xServer Management Console for live operations, in order to make sure that attackers cannot "browse" content, simply remove the complete subdirectory webapps/dashboard. This will undeploy the webapp dashboard.
To enable or to disable the console for single IPs or IP ranges see the setting core.security.adminAccessWhitelist.