Native Client Configuration
You configure the native client in two files:
gfcpp.properties 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.)
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
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.
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.
The typical configuration procedure for a native client includes the high-level steps listed below. The rest of this chapter provides the details.
- Place the
gfcpp.propertiesfile 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 gfcpp.properties Example File for a sample of the file format and contents.
- Place the
cache.xmlfile for the application in the desired location and specify its path in the
- Add other attributes to the
gfcpp.propertiesfile as needed for the local system architecture. See Attributes in gfcpp.properties for the configurable attributes, and gfcpp.properties Example File for a sample of the file format.
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.