|Setting System Properties / Configuring the Native Client and Cache Server|
You configure the native client in two files: gfcpp.properties for native client system-level configuration and cache.xml for cache-level configuration.
The gfcpp.properties file provides local settings required to connect a client to a distributed system, along with settings for licensing, logging, and statistics. See Attributes in gfcpp.properties.
The application software may include a set of gfcpp.properties 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 gfcpp.properties files, use any text editor to create them. See gfcpp.properties Example File for a sample of the file format and contents.
A native client looks for gfcpp.properties first in the working directory where the process runs, then in productDir/defaultSystem. Use the defaultSystem directory to group configuration files or to share them among processes for more convenient administration. If gfcpp.properties 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 gfcpp.properties (see Attributes in gfcpp.properties). If the cache.xml is not found, the process starts with an unconfigured cache.
If you start a native client without any configurations, it uses any attributes set programmatically plus any hard-coded defaults (listed in Attributes in gfcpp.properties). 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.