Allocating Direct Memory Space to Integration Server

To use BigMemory with Integration Server, you must allocate direct memory space to the JVM in which Integration Server is running.

The amount of direct memory space that is given to Integration Server is determined by the wrapper.java.additional.n=-XX:MaxDirectMemorySize property in the custom_wrapper.conf file. By default, the wrapper.java.additional.n=-XX:MaxDirectMemorySize property is not set when Integration Server is installed.

When you use BigMemory, you must set the wrapper.java.additional.n=-XX:MaxDirectMemorySize property to the amount of memory that you need to hold your off-heap caches.

Note: To allocate direct memory space to Microservices Runtime, add -XX:MaxDirectMemorySize to JAVA_CUSTOM_OPTs in Integration Server_directory /bin/setenv.bat(sh). For information about passing Java system properties to Microservices Runtime, see .

To allocate direct memory space to Integration Server

1. On the machine where Integration Server is installed, navigate to the following folder:

Software AG_directory \profiles\IS_instance_name\configuration

2. In a text editor, open custom_wrapper.conf.

3. Add a the wrapper.java.additional.n=-XX:MaxDirectMemorySize property to specify the amount of BigMemory required to accommodate all of your caches that use BigMemory. (This amount is limited by your Terracotta license, the amount of physical memory on your system, and how much of that memory is needed by the operating system and other applications running on the machine.)

For example, if you determine that you need 500 megabytes of BigMemory and you are running Integration Server under Windows, you would add the wrapper.java.additional property in the custom_wrapper.conf file to look like this:

wrapper.java.additional.n=-XX:MaxDirectMemorySize=500M

Where n is the next unused sequential number for the wrapper.java.additional properties in the file.

Note: You can express the value of this parameter using 'm' or 'M' for megabytes or using 'g' or 'G' for gigabytes.

4. Save and close custom_wrapper.conf.

5. Restart Integration Server.