Pivotal GemFire® Native Client v9.0

Native Client Configuration

You configure the native client in two files: for native client system-level configuration and cache.xml for cache-level configuration.

The configuration of the caches is part of the application development process. See Cache Initialization File. (The cache-level configuration file is generally referred to as cache.xml, but you can use any name.)

About Configuration File

The file provides local settings required to connect a client to a distributed system, along with settings for licensing, logging, and statistics. See Attributes in

The application software may include a set of files. You set any attributes needed for the application design in these files, then you can add any attributes needed for the local site.

If you do not have files, use any text editor to create them. See Example File for a sample of the file format and contents.

Configuration File Locations

A native client looks for first in the working directory where the process runs, then in product-dir/defaultSystem. Use the defaultSystem directory to group configuration files or to share them among processes for more convenient administration. If is not found, the process starts up with the default settings.

For the cache.xml cache configuration file, a native client looks for the path specified by the cache-xml-file attribute in (see Attributes in If the cache.xml is not found, the process starts with an unconfigured cache.

Configuring System Properties for the Native Client

The typical configuration procedure for a native client includes the high-level steps listed below. The rest of this chapter provides the details.

  1. Place the file for the application in the working directory or in product-dir/defaultSystem. Use the configuration file that came with the application software if there is one, or create your own. See Example File for a sample of the file format and contents.
  2. Place the cache.xml file for the application in the desired location and specify its path in the file.
  3. Add other attributes to the file as needed for the local system architecture. See Attributes in for the configurable attributes, and Example File for a sample of the file format.

Running a Native Client Out of the Box

If you start a native client without any configurations, it uses any attributes set programmatically plus any hard-coded defaults (listed in Attributes in Running with the defaults is a convenient way to learn the operation of the distributed system and to test which attributes need to be reconfigured for your environment.