Configuring the Remote Client Option

The Remote Client option lets client applications running on a networked Web or application server connect to a remote ScaleOut StateServer store. In this configuration, the StateServer service does not run on the Web or application server. This option installs as a separate component, as described in the section Components.

To configure the Remote Client option for access from a local server to a remote SOSS store, please follow these steps:

  1. Ensure that a secure, reliable, and fast network exists to the remote store. The network must be fast enough to handle the expected access bandwidth.
  2. On the remote SOSS store, configure a unique gateway IP address and gateway server port on all SOSS hosts. The IP address/port pair must be reachable from the local store using a TCP connection, and this pair must map to the SOSS server port on the remote host.

    [Note] Note

    The gateway IP address may be on a different subnet from that used for the remote store’s network interface. Also, if a router is used at the remote store and port mapping is employed, the gateway port may not match the SOSS server port’s value.

  3. On the local server, add a gateway to the Remote Client configuration using either the Management Console or the geos.exe command-line program (see Command-line Control Programs). To add a gateway, you enter one of the remote store’s gateway addresses in order to establish communications with the remote store. You can also optionally add additional gateway addresses for other SOSS hosts in the remote store in case one or more hosts are offline. Other gateway addresses also can be automatically populated as described below.

    [Note] Note

    The Remote Client configuration information is recorded in the client parameters file, soss_client_params.txt (see Configuration Parameters), which is stored in ScaleOut StateServer’s installation directory on the local server. This file separately may be used by the GeoServer option for configuring remote stores. It is never used by both components at the same time.

  4. If communication with the remote store is successful, you should be able to connect to the remote store with the management tools. You can use the Populate command to download the gateway addresses from all hosts on the remote store and save them in the local store’s client parameters file. This ensures that you can establish communications with the remote store if any of these gateway addresses respond. (Gateway addresses for offline hosts are ignored during remote access.)

    [Note] Note

    You should periodically re-run the Populate command if new hosts are added to the remote store.

    [Note] Note

    Gateway addresses are permanently stored in the client parameters file. If you know that a gateway address is no longer used at the remote store, you should remove it from the local store’s client parameters file using the management tools.