Main Steps to Deploying Configuration Files

These are the basic steps for deploying configuration files, with related detail in sections that follow.

1. Determine which configuration files you need for your installation.
2. Place the files in your directories or jar files.
3. For any file with a non-default name or location, provide the file specification in the system properties file and/or in the member class path. You can specify a member’s class path by using the --classpathoption for the gfsh start locator and start server commands.

GemFire Configuration Files

• gemfire.properties. Contains the settings required by members of a cluster. These settings include licensing, system member discovery, communication parameters, logging, and statistics. See the GemFire Properties Reference.
• gfsecurity.properties. An optional separate file that contains security-related (security-*) settings that are otherwise defined in gemfire.properties. Placing these member properties into a separate file allows you to restrict user access to those specific settings. See the GemFire Properties Reference.
• cache.xml. Declarative cache configuration file. This file contains XML declarations for cache, region, and region entry configuration. You also use it to configure disk stores, database login credentials, server and remote site location information, and socket information. See cache.xml.