This page describes an older version of the product. The latest stable version is 16.4.

Communication Filter

Filtering network communication across the WAN are done for two main reasons:

  1. Compressing the network traffic between the sites.
  2. Securing the network using SSL in case the communication between the sites is going over open WAN (not via VPN or other underlying encryption mechanisms).

Selecting the Filter

For compression the com.gigaspaces.lrmi.nio.filters.IOStreamCompressionFilterFactory should be used and for encryption com.gigaspaces.lrmi.nio.filters.SSLFilterFactory should be used. In both cases, you need to specify to which remote addresses this filter should be used, this is done be creating a config file which describes these addresses, putting it in the class path of the GSC (usually could be under <XAP Install>/config directory and pointing to it with a system property.

Address Matcher File Format

Each line in the file represents a regular expression which will be applied on the remote address when a connection is established. If any of the regular expressions in the file matches that address, the filter will be created on this communication channel.

For example, if you have three sites and you want to compress the communication only between these sites, you should have an address matcher file configured to point to the address of the other. It could be named “address-matcher.config”, placed under <XAP Install>/config of the gateway hosting machine. It should contain a line with a regular expression matching the remote sites gateway hosting machine address, lets assume its hostname is Site-A. The address matcher should look like this:


And on Site-A the address matcher file should look like this:


This file can contain more than one line and can be commented using the # char at the beginning of the line.

Configuring the Gateway GSC

If you are starting your own GSC that will host the gateway processing unit, you should start it with the following system properties:<filter name><file name>

If you use the built in mechanism which spawns a GSC to host the gateway you can specify custom jvm properties to be used when spawning the GSC either on the sink or delegator component (but only one of them):

<os-gateway:sink id="sink"  ...
  custom-jvm-properties="<filter name><file name>" />


<os-gateway:delegator id="delegator" ...
  custom-jvm-properties="<filter name><file name>" />