Administrator's Guide > Installation and Configuration > Wrapper Configuration

Wrapper Configuration

The wrapper.conf configuration file contains the settings for the wrapper process used to start, stop and restart the PTV 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.

Memory Settings

The wrapper sets the memory for the 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=1024

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

Management Console Activation

To disable the administrative PTV xServer Management Console for live operations, in order to make sure that attackers cannot "browse" content. Just uncomment the line

wrapper.java.additional.28=-DallowWeb=false

After a server restart, all web pages will then simply return a text saying ERR, and will not return an HTTP status since that might give hints to attackers.

Snippet Loader Base URI

If the snippet loader needs an explicit base URI, it can be set with an additional argument.

Example:

wrapper.java.additional.29=-DxServer.baseUri=http://localhost:12345