geode-docs/configuring/running/deploy_config_files_intro.html.md.erb - geode - Git at Google

 ---
 title:  Main Steps to Deploying Configuration Files
 ---

 <!--
 Licensed to the Apache Software Foundation (ASF) under one or more
 contributor license agreements.  See the NOTICE file distributed with
 this work for additional information regarding copyright ownership.
 The ASF licenses this file to You under the Apache License, Version 2.0
 (the "License"); you may not use this file except in compliance with
 the License.  You may obtain a copy of the License at

      http://www.apache.org/licenses/LICENSE-2.0

 Unless required by applicable law or agreed to in writing, software
 distributed under the License is distributed on an "AS IS" BASIS,
 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 See the License for the specific language governing permissions and
 limitations under the License.
 -->

 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 `CLASSPATH.`

 ## <a id="concept_337B365782E44951B73F33E1E17AB07B__section_53C98F9DB1584E3BABFA315CDF254A92" class="no-quick-link"></a><%=vars.product_name%> 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 [<%=vars.product_name%> Properties Reference](../../reference/topics/gemfire_properties.html).
 -   **`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 [<%=vars.product_name%> Properties Reference](../../reference/topics/gemfire_properties.html).
 -   `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](../../reference/topics/chapter_overview_cache_xml.html#cache_xml).
	---
	title: Main Steps to Deploying Configuration Files
	---

	<!--
	Licensed to the Apache Software Foundation (ASF) under one or more
	contributor license agreements. See the NOTICE file distributed with
	this work for additional information regarding copyright ownership.
	The ASF licenses this file to You under the Apache License, Version 2.0
	(the "License"); you may not use this file except in compliance with
	the License. You may obtain a copy of the License at

	http://www.apache.org/licenses/LICENSE-2.0

	Unless required by applicable law or agreed to in writing, software
	distributed under the License is distributed on an "AS IS" BASIS,
	WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
	See the License for the specific language governing permissions and
	limitations under the License.
	-->

	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 `CLASSPATH.`

	## <a id="concept_337B365782E44951B73F33E1E17AB07B__section_53C98F9DB1584E3BABFA315CDF254A92" class="no-quick-link"></a><%=vars.product_name%> 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 [<%=vars.product_name%> Properties Reference](../../reference/topics/gemfire_properties.html).
	- `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 [<%=vars.product_name%> Properties Reference](../../reference/topics/gemfire_properties.html).
	- `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](../../reference/topics/chapter_overview_cache_xml.html#cache_xml).