You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@geode.apache.org by db...@apache.org on 2017/08/12 00:03:27 UTC
geode git commit: GEODE-3395 Variable-ize product version and name in
user guide - Getting Started
Repository: geode
Updated Branches:
refs/heads/develop 915568415 -> 0e6bf546e
GEODE-3395 Variable-ize product version and name in user guide - Getting Started
Project: http://git-wip-us.apache.org/repos/asf/geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/geode/commit/0e6bf546
Tree: http://git-wip-us.apache.org/repos/asf/geode/tree/0e6bf546
Diff: http://git-wip-us.apache.org/repos/asf/geode/diff/0e6bf546
Branch: refs/heads/develop
Commit: 0e6bf546e0e3282b53d90bce4dbe1c0c1be1fa02
Parents: 9155684
Author: Dave Barnes <db...@pivotal.io>
Authored: Fri Aug 11 17:01:33 2017 -0700
Committer: Dave Barnes <db...@pivotal.io>
Committed: Fri Aug 11 17:02:46 2017 -0700
----------------------------------------------------------------------
geode-book/Gemfile.lock | 107 ++++++++++---------
.../15_minute_quickstart_gfsh.html.md.erb | 41 ++++---
.../getting_started/book_intro.html.md.erb | 18 ++--
.../getting_started/geode_overview.html.md.erb | 16 ++-
.../installation/install_standalone.html.md.erb | 10 +-
.../getting_started/product_intro.html.md.erb | 2 +-
.../querying_quick_reference.html.md.erb | 28 +++--
.../getting_started/setup_classpath.html.md.erb | 26 ++---
.../host_machine.html.md.erb | 4 +-
.../getting_started/uninstall_geode.html.md.erb | 4 +-
10 files changed, 122 insertions(+), 134 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/geode/blob/0e6bf546/geode-book/Gemfile.lock
----------------------------------------------------------------------
diff --git a/geode-book/Gemfile.lock b/geode-book/Gemfile.lock
index ed2fbd6..5f6b59a 100644
--- a/geode-book/Gemfile.lock
+++ b/geode-book/Gemfile.lock
@@ -1,23 +1,23 @@
GEM
remote: https://rubygems.org/
specs:
- activesupport (4.2.7.1)
+ activesupport (4.2.9)
i18n (~> 0.7)
- json (~> 1.7, >= 1.7.7)
minitest (~> 5.1)
thread_safe (~> 0.3, >= 0.3.4)
tzinfo (~> 1.1)
- addressable (2.4.0)
+ addressable (2.5.1)
+ public_suffix (~> 2.0, >= 2.0.2)
ansi (1.5.0)
- backports (3.6.8)
- bookbindery (10.0.2)
+ backports (3.8.0)
+ bookbindery (10.1.7)
ansi (~> 1.4)
css_parser
elasticsearch
fog-aws (~> 0.7.1)
font-awesome-sass
git (~> 1.2.8)
- middleman
+ middleman (= 4.1.10)
middleman-compass
middleman-livereload
middleman-sprockets
@@ -28,13 +28,13 @@ GEM
redcarpet (~> 3.2.3)
rouge (!= 1.9.1)
therubyracer
- thor
- builder (3.2.2)
- chunky_png (1.3.7)
+ thor (= 0.19.1)
+ builder (3.2.3)
+ chunky_png (1.3.8)
coffee-script (2.4.1)
coffee-script-source
execjs
- coffee-script-source (1.10.0)
+ coffee-script-source (1.12.2)
compass (1.0.3)
chunky_png (~> 1.2)
compass-core (~> 1.0.2)
@@ -47,66 +47,65 @@ GEM
sass (>= 3.3.0, < 3.5)
compass-import-once (1.0.5)
sass (>= 3.2, < 3.5)
- concurrent-ruby (1.0.2)
+ concurrent-ruby (1.0.5)
contracts (0.13.0)
- css_parser (1.4.5)
+ css_parser (1.5.0)
addressable
- dotenv (2.1.1)
- elasticsearch (2.0.0)
- elasticsearch-api (= 2.0.0)
- elasticsearch-transport (= 2.0.0)
- elasticsearch-api (2.0.0)
+ dotenv (2.2.1)
+ elasticsearch (5.0.4)
+ elasticsearch-api (= 5.0.4)
+ elasticsearch-transport (= 5.0.4)
+ elasticsearch-api (5.0.4)
multi_json
- elasticsearch-transport (2.0.0)
+ elasticsearch-transport (5.0.4)
faraday
multi_json
em-websocket (0.5.1)
eventmachine (>= 0.12.9)
http_parser.rb (~> 0.6.0)
erubis (2.7.0)
- eventmachine (1.2.0.1)
- excon (0.54.0)
+ eventmachine (1.2.5)
+ excon (0.58.0)
execjs (2.7.0)
- faraday (0.9.2)
+ faraday (0.12.2)
multipart-post (>= 1.2, < 3)
fast_blank (1.0.0)
- fastimage (2.0.0)
- addressable (~> 2)
- ffi (1.9.14)
+ fastimage (2.1.0)
+ ffi (1.9.18)
fog-aws (0.7.6)
fog-core (~> 1.27)
fog-json (~> 1.0)
fog-xml (~> 0.1)
ipaddress (~> 0.8)
- fog-core (1.43.0)
+ fog-core (1.45.0)
builder
- excon (~> 0.49)
+ excon (~> 0.58)
formatador (~> 0.2)
fog-json (1.0.2)
fog-core (~> 1.0)
multi_json (~> 1.10)
- fog-xml (0.1.2)
+ fog-xml (0.1.3)
fog-core
- nokogiri (~> 1.5, >= 1.5.11)
- font-awesome-sass (4.6.2)
+ nokogiri (>= 1.5.11, < 2.0.0)
+ font-awesome-sass (4.7.0)
sass (>= 3.2)
formatador (0.2.5)
git (1.2.9.1)
- haml (4.0.7)
+ haml (5.0.2)
+ temple (>= 0.8.0)
tilt
hamster (3.0.0)
concurrent-ruby (~> 1.0)
- hashie (3.4.6)
+ hashie (3.5.6)
http_parser.rb (0.6.0)
i18n (0.7.0)
ipaddress (0.8.3)
- json (1.8.3)
- kramdown (1.12.0)
+ kramdown (1.14.0)
libv8 (3.16.14.7)
listen (3.0.8)
rb-fsevent (~> 0.9, >= 0.9.4)
rb-inotify (~> 0.9, >= 0.9.7)
- memoist (0.15.0)
+ memoist (0.16.0)
middleman (4.1.10)
coffee-script (~> 2.2)
compass-import-once (= 1.0.5)
@@ -147,50 +146,52 @@ GEM
em-websocket (~> 0.5.1)
middleman-core (>= 3.3)
rack-livereload (~> 0.3.15)
- middleman-sprockets (4.0.0)
+ middleman-sprockets (4.1.0)
middleman-core (~> 4.0)
sprockets (>= 3.0)
middleman-syntax (3.0.0)
middleman-core (>= 3.2)
rouge (~> 2.0)
mini_portile2 (2.0.0)
- minitest (5.9.1)
+ minitest (5.10.3)
multi_json (1.12.1)
multipart-post (2.0.0)
nokogiri (1.6.7.2)
mini_portile2 (~> 2.0.0.rc2)
- padrino-helpers (0.13.3.2)
+ padrino-helpers (0.13.3.4)
i18n (~> 0.6, >= 0.6.7)
- padrino-support (= 0.13.3.2)
+ padrino-support (= 0.13.3.4)
tilt (>= 1.4.1, < 3)
- padrino-support (0.13.3.2)
+ padrino-support (0.13.3.4)
activesupport (>= 3.1)
- parallel (1.9.0)
- puma (3.6.0)
- rack (1.6.4)
+ parallel (1.12.0)
+ public_suffix (2.0.5)
+ puma (3.9.1)
+ rack (1.6.8)
rack-livereload (0.3.16)
rack
rack-rewrite (1.5.1)
- rb-fsevent (0.9.7)
- rb-inotify (0.9.7)
- ffi (>= 0.5.0)
+ rb-fsevent (0.10.2)
+ rb-inotify (0.9.10)
+ ffi (>= 0.5.0, < 2)
redcarpet (3.2.3)
ref (2.0.0)
- rouge (2.0.6)
- sass (3.4.22)
- servolux (0.12.0)
- sprockets (3.7.0)
+ rouge (2.1.1)
+ sass (3.4.25)
+ servolux (0.13.0)
+ sprockets (3.7.1)
concurrent-ruby (~> 1.0)
rack (> 1, < 3)
+ temple (0.8.0)
therubyracer (0.12.2)
libv8 (~> 3.16.14.0)
ref
thor (0.19.1)
- thread_safe (0.3.5)
+ thread_safe (0.3.6)
tilt (1.4.1)
- tzinfo (1.2.2)
+ tzinfo (1.2.3)
thread_safe (~> 0.1)
- uglifier (3.0.2)
+ uglifier (3.2.0)
execjs (>= 0.3.0, < 3)
PLATFORMS
@@ -201,4 +202,4 @@ DEPENDENCIES
libv8 (= 3.16.14.7)
BUNDLED WITH
- 1.13.1
+ 1.13.6
http://git-wip-us.apache.org/repos/asf/geode/blob/0e6bf546/geode-docs/getting_started/15_minute_quickstart_gfsh.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/getting_started/15_minute_quickstart_gfsh.html.md.erb b/geode-docs/getting_started/15_minute_quickstart_gfsh.html.md.erb
index 6e5e23e..36c2ccf 100644
--- a/geode-docs/getting_started/15_minute_quickstart_gfsh.html.md.erb
+++ b/geode-docs/getting_started/15_minute_quickstart_gfsh.html.md.erb
@@ -1,6 +1,4 @@
----
-title: Apache Geode in 15 Minutes or Less
----
+<% set_title(product_name_long, "in 15 Minutes or Less") %>
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
@@ -20,17 +18,17 @@ limitations under the License.
-->
<a id="topic_FE3F28ED18E145F787431EC87B676A76"></a>
-Need a quick introduction to Apache Geode? Take this brief tour to try out basic features and functionality.
+Need a quick introduction to <%=vars.product_name_long%>? Take this brief tour to try out basic features and functionality.
-## <a id="topic_FE3F28ED18E145F787431EC87B676A76__section_ECE5170BAD9B454E875F13BEB5762DDD" class="no-quick-link"></a>Step 1: Install Apache Geode
+## <a id="topic_FE3F28ED18E145F787431EC87B676A76__section_ECE5170BAD9B454E875F13BEB5762DDD" class="no-quick-link"></a>Step 1: Install <%=vars.product_name_long%>
See [How to Install](installation/install_standalone.html#concept_0129F6A1D0EB42C4A3D24861AF2C5425) for instructions.
## <a id="topic_FE3F28ED18E145F787431EC87B676A76__section_582F8CBBD99D42F1A55C07591E2E9E9E" class="no-quick-link"></a>Step 2: Use gfsh to start a locator
-In a terminal window, use the `gfsh` command line interface to start up a locator. Apache Geode *gfsh* (pronounced "jee-fish") provides a single, intuitive command-line interface from which you can launch, manage, and monitor Apache Geode processes, data, and applications. See [gfsh](../tools_modules/gfsh/chapter_overview.html).
+In a terminal window, use the `gfsh` command line interface to start up a locator. <%=vars.product_name_long%> *gfsh* (pronounced "jee-fish") provides a single, intuitive command-line interface from which you can launch, manage, and monitor <%=vars.product_name_long%> processes, data, and applications. See [gfsh](../tools_modules/gfsh/chapter_overview.html).
-The *locator* is a Geode process that tells new, connecting members where running members are located and provides load balancing for server use. A locator, by default, starts up a JMX Manager, which is used for monitoring and managing a Geode cluster. The cluster configuration service uses locators to persist and distribute cluster configurations to cluster members. See [Running Geode Locator Processes](../configuring/running/running_the_locator.html) and [Overview of the Cluster Configuration Service](../configuring/cluster_config/gfsh_persist.html).
+The *locator* is a <%=vars.product_name%> process that tells new, connecting members where running members are located and provides load balancing for server use. A locator, by default, starts up a JMX Manager, which is used for monitoring and managing a <%=vars.product_name%> cluster. The cluster configuration service uses locators to persist and distribute cluster configurations to cluster members. See [Running <%=vars.product_name%> Locator Processes](../configuring/running/running_the_locator.html) and [Overview of the Cluster Configuration Service](../configuring/cluster_config/gfsh_persist.html).
1. Create a scratch working directory (for example, `my_geode`) and change directories into it. `gfsh` saves locator and server working directories and log files in this location.
2. Start gfsh by typing `gfsh` at the command line (or `gfsh.bat` if you are using Windows).
@@ -40,9 +38,9 @@ The *locator* is a Geode process that tells new, connecting members where runnin
/ _____/ ______/ ______/ /____/ /
/ / __/ /___ /_____ / _____ /
/ /__/ / ____/ _____/ / / / /
- /______/_/ /______/_/ /_/ 1.0.0
+ /______/_/ /______/_/ /_/ <%=vars.product_version%>
- Monitor and Manage Geode
+ Monitor and Manage <%=vars.product_name%>
gfsh>
```
@@ -50,12 +48,12 @@ The *locator* is a Geode process that tells new, connecting members where runnin
``` pre
gfsh>start locator --name=locator1
- Starting a Geode Locator in /home/username/my_geode/locator1...
+ Starting a <%=vars.product_name%> Locator in /home/username/my_geode/locator1...
.................................
Locator in /home/username/my_geode/locator1 on ubuntu.local[10334] as locator1 is currently online.
Process ID: 3529
Uptime: 18 seconds
- Geode Version: 1.0.0
+ <%=vars.product_name%> Version: <%=vars.product_version%>
Java Version: 1.8.0_101
Log File: /home/username/my_geode/locator1/locator1.log
JVM Arguments: -Dgemfire.enable-cluster-configuration=true -Dgemfire.load-cluster-configuration-from-dir=false
@@ -73,7 +71,7 @@ If you run `start locator` from gfsh without specifying the member name, gfsh wi
## <a id="topic_FE3F28ED18E145F787431EC87B676A76__section_02C79BFFB5334E78A5856AE1EB1F1F84" class="no-quick-link"></a>Step 3: Start Pulse
-Start up the browser-based Pulse monitoring tool. Pulse is a Web Application that provides a graphical dashboard for monitoring vital, real-time health and performance of Geode clusters, members, and regions. See [Geode Pulse](../tools_modules/pulse/pulse-overview.html).
+Start up the browser-based Pulse monitoring tool. Pulse is a Web Application that provides a graphical dashboard for monitoring vital, real-time health and performance of <%=vars.product_name%> clusters, members, and regions. See [<%=vars.product_name%> Pulse](../tools_modules/pulse/pulse-overview.html).
``` pre
gfsh>start pulse
@@ -87,13 +85,12 @@ The Pulse application now displays the locator you just started (locator1):
## <a id="topic_FE3F28ED18E145F787431EC87B676A76__section_C617BC1C70EB41B8BCA3691D6E3C891A" class="no-quick-link"></a>Step 4: Start a server
-A Geode server is a process that runs as a long-lived, configurable member of a cluster (also called a *distributed system*). The Geode server is used primarily for hosting long-lived data regions and for running standard Geode processes such as the server in a client/server configuration. See [Running Geode Server Processes](../configuring/running/running_the_cacheserver.html).
+A <%=vars.product_name%> server is a process that runs as a long-lived, configurable member of a cluster (also called a *distributed system*). The <%=vars.product_name%> server is used primarily for hosting long-lived data regions and for running standard <%=vars.product_name%> processes such as the server in a client/server configuration. See [Running <%=vars.product_name%> Server Processes](../configuring/running/running_the_cacheserver.html).
Start the cache server:
``` pre
gfsh>start server --name=server1 --server-port=40411
-
```
This commands starts a cache server named "server1" on the specified port of 40411.
@@ -104,7 +101,7 @@ Observe the changes (new member and server) in Pulse. Try expanding the distribu
## <a id="topic_FE3F28ED18E145F787431EC87B676A76__section_3EA12E44B8394C6A9302DF4D14888AF4" class="no-quick-link"></a>Step 5: Create a replicated, persistent region
-In this step you create a region with the `gfsh` command line utility. Regions are the core building blocks of the Geode cluster and provide the means for organizing your data. The region you create for this exercise employs replication to replicate data across members of the cluster and utilizes persistence to save the data to disk. See [Data Regions](../basic_config/data_regions/chapter_overview.html#data_regions).
+In this step you create a region with the `gfsh` command line utility. Regions are the core building blocks of the <%=vars.product_name%> cluster and provide the means for organizing your data. The region you create for this exercise employs replication to replicate data across members of the cluster and utilizes persistence to save the data to disk. See [Data Regions](../basic_config/data_regions/chapter_overview.html#data_regions).
1. Create a replicated, persistent region:
@@ -158,7 +155,7 @@ In this step you create a region with the `gfsh` command line utility. Regions a
## Step 6: Manipulate data in the region and demonstrate persistence
-Apache Geode manages data as key/value pairs. In most applications, a Java program adds, deletes and modifies stored data. You can also use gfsh commands to add and retrieve data. See [Data Commands](../tools_modules/gfsh/quick_ref_commands_by_area.html#topic_C7DB8A800D6244AE8FF3ADDCF139DCE4).
+<%=vars.product_name_long%> manages data as key/value pairs. In most applications, a Java program adds, deletes and modifies stored data. You can also use gfsh commands to add and retrieve data. See [Data Commands](../tools_modules/gfsh/quick_ref_commands_by_area.html#topic_C7DB8A800D6244AE8FF3ADDCF139DCE4).
1. Run the following `put` commands to add some data to the region:
@@ -231,7 +228,7 @@ Apache Geode manages data as key/value pairs. In most applications, a Java progr
one
```
- Because regionA uses persistence, it writes a copy of the data to disk. When a server hosting regionA starts, the data is populated into the cache. Note that the result displays the values for the two data entries you created with the `put` commands prior to stopping the server≈.
+ Because regionA uses persistence, it writes a copy of the data to disk. When a server hosting regionA starts, the data is populated into the cache. Note that the result displays the values for the two data entries you created with the `put` commands prior to stopping the server.
See [Data Entries](../basic_config/data_entries_custom_classes/chapter_overview.html).
@@ -354,7 +351,7 @@ In this step you restart the cache servers in parallel. Because the data is pers
``` pre
gfsh>start server --name=server1 --server-port=40411
- Starting a Geode Server in /home/username/my_geode/server1...
+ Starting a <%=vars.product_name%> Server in /home/username/my_geode/server1...
............................................................................
............................................................................
```
@@ -388,9 +385,9 @@ In this step you restart the cache servers in parallel. Because the data is pers
/ _____/ ______/ ______/ /____/ /
/ / __/ /___ /_____ / _____ /
/ /__/ / ____/ _____/ / / / /
- /______/_/ /______/_/ /_/ 1.0.0
+ /______/_/ /______/_/ /_/ <%=vars.product_version%>
- Monitor and Manage Geode
+ Monitor and Manage <%=vars.product_name%>
```
3. Run the following command to connect to the cluster:
@@ -414,7 +411,7 @@ In this step you restart the cache servers in parallel. Because the data is pers
Server in /home/username/my_geode/server1 on ubuntu.local[40411] as server1 is currently online.
Process ID: 3402
Uptime: 1 minute 46 seconds
- Geode Version: 1.0.0
+ <%=vars.product_name%> Version: <%=vars.product_version%>
Java Version: 1.8.0_60
Log File: /home/username/my_geode/server1/server1.log
JVM Arguments: -Dgemfire.default.locators=192.0.2.0[10334] -Dgemfire.use-cluster-configuration=true
@@ -513,7 +510,7 @@ To shut down your cluster, do the following:
## <a id="topic_FE3F28ED18E145F787431EC87B676A76__section_C8694C6BB07E4430A73DDD72ABB473F1" class="no-quick-link"></a>Step 10: What to do next...
-Here are some suggestions on what to explore next with Apache Geode:
+Here are some suggestions on what to explore next with <%=vars.product_name_long%>:
- Continue reading the next section to learn more about the components and concepts that were just introduced.
- To get more practice using `gfsh`, see [Tutorial—Performing Common Tasks with gfsh](../tools_modules/gfsh/tour_of_gfsh.html#concept_0B7DE9DEC1524ED0897C144EE1B83A34).
http://git-wip-us.apache.org/repos/asf/geode/blob/0e6bf546/geode-docs/getting_started/book_intro.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/getting_started/book_intro.html.md.erb b/geode-docs/getting_started/book_intro.html.md.erb
index 4685311..9e3f187 100644
--- a/geode-docs/getting_started/book_intro.html.md.erb
+++ b/geode-docs/getting_started/book_intro.html.md.erb
@@ -1,6 +1,4 @@
----
-title: Getting Started with Apache Geode
----
+<% set_title("Getting Started with", product_name_long) %>
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
@@ -21,20 +19,20 @@ limitations under the License.
A tutorial demonstrates features, and a main features section describes key functionality.
-- **[About Apache Geode](geode_overview.html)**
+- **[About <%=vars.product_name_long%>](geode_overview.html)**
- Apache Geode is a data management platform that provides real-time, consistent access to data-intensive applications throughout widely distributed cloud architectures.
+ <%=vars.product_name_long%> is a data management platform that provides real-time, consistent access to data-intensive applications throughout widely distributed cloud architectures.
-- **[Main Features of Apache Geode](product_intro.html)**
+- **[Main Features of <%=vars.product_name_long%>](product_intro.html)**
- This section summarizes the main features and key functionality of Apache Geode.
+ This section summarizes the main features and key functionality of <%=vars.product_name_long%>.
- **[Prerequisites and Installation Instructions](../prereq_and_install.html)**
- Each host of Apache Geode that meets a small set of prerequisites may follow the provided installation instructions.
+ Each host of <%=vars.product_name_long%> that meets a small set of prerequisites may follow the provided installation instructions.
-- **[Apache Geode in 15 Minutes or Less](15_minute_quickstart_gfsh.html)**
+- **[<%=vars.product_name_long%> in 15 Minutes or Less](15_minute_quickstart_gfsh.html)**
- Need a quick introduction to Apache Geode? Take this brief tour to try out basic features and functionality.
+ Need a quick introduction to <%=vars.product_name_long%>? Take this brief tour to try out basic features and functionality.
http://git-wip-us.apache.org/repos/asf/geode/blob/0e6bf546/geode-docs/getting_started/geode_overview.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/getting_started/geode_overview.html.md.erb b/geode-docs/getting_started/geode_overview.html.md.erb
index 6f5c31f..1dddd71 100644
--- a/geode-docs/getting_started/geode_overview.html.md.erb
+++ b/geode-docs/getting_started/geode_overview.html.md.erb
@@ -1,6 +1,4 @@
----
-title: About Apache Geode
----
+<% set_title("About", product_name_long)%>
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
@@ -19,19 +17,17 @@ See the License for the specific language governing permissions and
limitations under the License.
-->
-Apache Geode is a data management platform that provides real-time, consistent access to data-intensive applications throughout widely distributed cloud architectures.
+<%=vars.product_name_long%> is a data management platform that provides real-time, consistent access to data-intensive applications throughout widely distributed cloud architectures.
<a id="concept_3B5E445B19884680900161BDF25E32C9__section_itx_b41_mr"></a>
-Geode pools memory, CPU, network resources, and optionally local disk across multiple processes to manage application objects and behavior. It uses dynamic replication and data partitioning techniques to implement high availability, improved performance, scalability, and fault tolerance. In addition to being a distributed data container, Geode is an in-memory data management system that provides reliable asynchronous event notifications and guaranteed message delivery.
+<%=vars.product_name%> pools memory, CPU, network resources, and optionally local disk across multiple processes to manage application objects and behavior. It uses dynamic replication and data partitioning techniques to implement high availability, improved performance, scalability, and fault tolerance. In addition to being a distributed data container, <%=vars.product_name%> is an in-memory data management system that provides reliable asynchronous event notifications and guaranteed message delivery.
## <a id="concept_3B5E445B19884680900161BDF25E32C9__section_0031B81824874FC18F0828DB66150833" class="no-quick-link"></a>Main Concepts and Components
-*Caches* are an abstraction that describe a node in a Geode distributed system. Application architects can arrange these nodes in peer-to-peer or client/server topologies.
+*Caches* are an abstraction that describe a node in a <%=vars.product_name%> distributed system. Application architects can arrange these nodes in peer-to-peer or client/server topologies.
Within each cache, you define data *regions*. Data regions are analogous to tables in a relational database and manage data in a distributed fashion as name/value pairs. A *replicated* region stores identical copies of the data on each cache member of a distributed system. A *partitioned* region spreads the data among cache members. After the system is configured, client applications can access the distributed data in regions without knowledge of the underlying system architecture. You can define listeners to create notifications about when data has changed, and you can define expiration criteria to delete obsolete data in a region.
-For large production systems, Geode provides *locators*. Locators provide both discovery and load balancing services. You configure clients with a list of locator services and the locators maintain a dynamic list of member servers. By default, Geode clients and servers use port 40404 to discover each other.
+For large production systems, <%=vars.product_name%> provides *locators*. Locators provide both discovery and load balancing services. You configure clients with a list of locator services and the locators maintain a dynamic list of member servers. By default, <%=vars.product_name%> clients and servers use port 40404 to discover each other.
-<a id="concept_3B5E445B19884680900161BDF25E32C9__section_zrl_c41_mr"></a>
-
-For more information on product features, see [Main Features of Apache Geode](product_intro.html).
+For more information on product features, see [Main Features of <%=vars.product_name_long%>](product_intro.html).
http://git-wip-us.apache.org/repos/asf/geode/blob/0e6bf546/geode-docs/getting_started/installation/install_standalone.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/getting_started/installation/install_standalone.html.md.erb b/geode-docs/getting_started/installation/install_standalone.html.md.erb
index a063ea5..b6d4da9 100644
--- a/geode-docs/getting_started/installation/install_standalone.html.md.erb
+++ b/geode-docs/getting_started/installation/install_standalone.html.md.erb
@@ -1,6 +1,4 @@
----
-title: How to Install
----
+<% set_title("How to Install", product_name_long)%>
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
@@ -19,7 +17,7 @@ See the License for the specific language governing permissions and
limitations under the License.
-->
-Build from source or use the ZIP or TAR distribution to install Apache Geode on every physical and virtual machine that will run Apache Geode.
+Build from source or use the ZIP or TAR distribution to install <%=vars.product_name_long%> on every physical and virtual machine that will run <%=vars.product_name_long%>.
## Build from Source on Unix
@@ -109,7 +107,7 @@ Build from source or use the ZIP or TAR distribution to install Apache Geode on
set JAVA_HOME=c:\Program Files\Java\jdk1.8.0_60
```
-4. Add the Geode scripts to your PATH environment variable. On Linux/Unix platforms:
+4. Add the <%=vars.product_name%> scripts to your PATH environment variable. On Linux/Unix platforms:
``` pre
PATH=$PATH:$JAVA_HOME/bin:path_to_product/bin
@@ -122,7 +120,7 @@ Build from source or use the ZIP or TAR distribution to install Apache Geode on
set PATH=%PATH%;%JAVA_HOME%\bin;path_to_product\bin
```
-5. To verify the installation, type `gfsh version` at the command line and note that the output lists the installed version of Geode. For example:
+5. To verify the installation, type `gfsh version` at the command line and note that the output lists the installed version of <%=vars.product_name%>. For example:
``` pre
$ gfsh version
http://git-wip-us.apache.org/repos/asf/geode/blob/0e6bf546/geode-docs/getting_started/product_intro.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/getting_started/product_intro.html.md.erb b/geode-docs/getting_started/product_intro.html.md.erb
index 103b2dd..e873fac 100644
--- a/geode-docs/getting_started/product_intro.html.md.erb
+++ b/geode-docs/getting_started/product_intro.html.md.erb
@@ -97,7 +97,7 @@ At the core of this architecture is the gateway sender configuration used for di
## <a id="concept_3B5E445B19884680900161BDF25E32C9__section_FF4C3B6E26104C4D93186F6FFE22B321" class="no-quick-link"></a>Continuous Querying
-In messaging systems like Java Message Service, clients subscribe to topics and queues. Any message delivered to a topic is sent to the subscriber. Geode allows continuous querying by having applications express complex interest using Object Query Language.
+In messaging systems like Java Message Service, clients subscribe to topics and queues. Any message delivered to a topic is sent to the subscriber. <%=vars.product_name%> allows continuous querying by having applications express complex interest using Object Query Language.
## <a id="mainfeatures_heterogeneousdatasharing" class="no-quick-link"></a>Heterogeneous Data Sharing
http://git-wip-us.apache.org/repos/asf/geode/blob/0e6bf546/geode-docs/getting_started/querying_quick_reference.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/getting_started/querying_quick_reference.html.md.erb b/geode-docs/getting_started/querying_quick_reference.html.md.erb
index 74ea3eb..3f49737 100644
--- a/geode-docs/getting_started/querying_quick_reference.html.md.erb
+++ b/geode-docs/getting_started/querying_quick_reference.html.md.erb
@@ -1,6 +1,4 @@
----
-title: Geode Querying FAQ and Examples
----
+<% set_title(product_name, "Querying FAQ and Examples")%>
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
@@ -19,12 +17,12 @@ See the License for the specific language governing permissions and
limitations under the License.
-->
-This topic answers some frequently asked questions on querying functionality. It provides examples to help you get started with Geode querying.
+This topic answers some frequently asked questions on querying functionality. It provides examples to help you get started with <%=vars.product_name%> querying.
<a id="reference_D5CE64F5FD6F4A808AEFB748C867189E__section_AFAD97A4BA2D45CF91ED1525A54DDFD6"></a>
-For additional information on Geode querying, see [Querying](../developing/querying_basics/chapter_overview.html).
+For additional information on <%=vars.product_name%> querying, see [Querying](../developing/querying_basics/chapter_overview.html).
-- [How do I write and execute a query against a Geode region?](querying_quick_reference.html#reference_D5CE64F5FD6F4A808AEFB748C867189E__section_7A4D2C6A4E2C4F4384C158FFCA9CA1C0)
+- [How do I write and execute a query against a <%=vars.product_name%> region?](querying_quick_reference.html#reference_D5CE64F5FD6F4A808AEFB748C867189E__section_7A4D2C6A4E2C4F4384C158FFCA9CA1C0)
- [Can I see query string examples, listed by query type?](querying_quick_reference.html#reference_D5CE64F5FD6F4A808AEFB748C867189E__section_641D97CD874D4182961C85429ACA1B05)
- [Which APIs should I use to write my queries?](querying_quick_reference.html#reference_D5CE64F5FD6F4A808AEFB748C867189E__section_5383407F9D004D4EB4E695252EBA1EF0)
- [How do I invoke an object's method in a query?](querying_quick_reference.html#reference_D5CE64F5FD6F4A808AEFB748C867189E__section_3E6E4B33D57846008EF4404D2B687597)
@@ -34,20 +32,20 @@ For additional information on Geode querying, see [Querying](../developing/query
- [How do I create an index?](querying_quick_reference.html#reference_D5CE64F5FD6F4A808AEFB748C867189E__section_76CDCCFBDB134A339DBE556C28D48F11)
- [Can I query a partitioned region? Can I perform a join query on a partitioned region?](querying_quick_reference.html#reference_D5CE64F5FD6F4A808AEFB748C867189E__section_EDD17817450C4FC0B510CD87DB2FCD16)
- [How can I improve the performance of a partitioned region query?](querying_quick_reference.html#reference_D5CE64F5FD6F4A808AEFB748C867189E__section_5FF905E0D10D4CDF9E6F49A70848AF69)
-- [Which query language elements are supported in Geode?](querying_quick_reference.html#reference_D5CE64F5FD6F4A808AEFB748C867189E__section_FBC59A5420FD40D6907A302A1D50DF7E)
+- [Which query language elements are supported in <%=vars.product_name%>?](querying_quick_reference.html#reference_D5CE64F5FD6F4A808AEFB748C867189E__section_FBC59A5420FD40D6907A302A1D50DF7E)
- [How do I debug queries?](querying_quick_reference.html#reference_D5CE64F5FD6F4A808AEFB748C867189E__section_314B88A55B514B88A12DC36227A2D4EF)
- [Can I use implicit attributes or methods in my query?](#reference_D5CE64F5FD6F4A808AEFB748C867189E__implicit_attributes)
- [How do I perform a case-insensitive search on a field in OQL?](#reference_D5CE64F5FD6F4A808AEFB748C867189E__section_ayq_hqw_1r)
-## <a id="reference_D5CE64F5FD6F4A808AEFB748C867189E__section_7A4D2C6A4E2C4F4384C158FFCA9CA1C0" class="no-quick-link"></a>How do I write and execute a query against a Geode region?
+## <a id="reference_D5CE64F5FD6F4A808AEFB748C867189E__section_7A4D2C6A4E2C4F4384C158FFCA9CA1C0" class="no-quick-link"></a>How do I write and execute a query against a <%=vars.product_name%> region?
-To write and execute a query in Geode, you can use any of the following mechanisms. Sample query code follows.
+To write and execute a query in <%=vars.product_name%>, you can use any of the following mechanisms. Sample query code follows.
-- Geode querying APIs
+- <%=vars.product_name%> querying APIs
- [gfsh](../tools_modules/gfsh/chapter_overview.html) command-line interface; in particular the [query](../tools_modules/gfsh/command-pages/query.html) command
- REST API [query endpoints](../rest_apps/rest_queries.html#concept_mmg_d35_m4)
-**Sample Geode Query Code (Java)**
+**Sample <%=vars.product_name%> Query Code (Java)**
``` pre
// Identify your query string.
@@ -89,7 +87,7 @@ class Position implements DataSerializable {
**Basic WHERE Clause Examples**
-In the following examples, the status field is type String and the ID field is type int. See [Supported Literals](../developing/query_additional/literals.html#literals) for a complete list of literals supported in Geode querying.
+In the following examples, the status field is type String and the ID field is type int. See [Supported Literals](../developing/query_additional/literals.html#literals) for a complete list of literals supported in <%=vars.product_name%> querying.
1. Select all active portfolios.
@@ -615,7 +613,7 @@ For a full list of restrictions, see [Partitioned Region Query Restrictions](../
If you know the data you need to query, you can target particular nodes in your queries (thus reducing the number of servers the query needs to access) by executing the query with the FunctionService. See [Querying a Partitioned Region on a Single Node](../developing/query_additional/query_on_a_single_node.html#concept_30B18A6507534993BD55C2C9E0544A97) for details. If you are querying data that has been partitioned by a key or specific field, you should first create a key index and then execute the query using the FunctionService with the key or field as a filter. See [Optimizing Queries on Data Partitioned by a Key or Field Value](../developing/query_additional/partitioned_region_key_or_field_value.html#concept_3010014DFBC9479783B2B45982014454).
-## <a id="reference_D5CE64F5FD6F4A808AEFB748C867189E__section_FBC59A5420FD40D6907A302A1D50DF7E" class="no-quick-link"></a>Which query language elements are supported in Geode?
+## <a id="reference_D5CE64F5FD6F4A808AEFB748C867189E__section_FBC59A5420FD40D6907A302A1D50DF7E" class="no-quick-link"></a>Which query language elements are supported in <%=vars.product_name%>?
| Supported elements || |
|----------|----------|----------|
@@ -647,7 +645,7 @@ You can also write:
<TRACE> SELECT * FROM /exampleRegion
```
-When the query is executed, Geode will log a message in `$GEMFIRE_DIR/system.log` with the following information:
+When the query is executed, <%=vars.product_name%> will log a message in `$GEMFIRE_DIR/system.log` with the following information:
``` pre
[info 2011/08/29 11:24:35.472 PDT CqServer <main> tid=0x1] Query Executed in 9.619656 ms; rowCount = 99;
@@ -668,7 +666,7 @@ System.setProperty("gemfire.Query.VERBOSE","true");
## <a id="reference_D5CE64F5FD6F4A808AEFB748C867189E__implicit_attributes" class="no-quick-link"></a>Can I use implicit attributes or methods in my query?
-If an implicit attribute or method name can only be associated with one untyped iterator, the Geode query processor will assume that it is associated with that iterator. However, if more than one untyped iterator is in scope, then the query will fail with a `TypeMismatchException`. The following query fails because the query processor does not fully type expressions:
+If an implicit attribute or method name can only be associated with one untyped iterator, the <%=vars.product_name%> query processor will assume that it is associated with that iterator. However, if more than one untyped iterator is in scope, then the query will fail with a `TypeMismatchException`. The following query fails because the query processor does not fully type expressions:
``` pre
select distinct value.secId from /pos , getPositions(23)
http://git-wip-us.apache.org/repos/asf/geode/blob/0e6bf546/geode-docs/getting_started/setup_classpath.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/getting_started/setup_classpath.html.md.erb b/geode-docs/getting_started/setup_classpath.html.md.erb
index b12ba12..c188e3c 100644
--- a/geode-docs/getting_started/setup_classpath.html.md.erb
+++ b/geode-docs/getting_started/setup_classpath.html.md.erb
@@ -19,14 +19,14 @@ See the License for the specific language governing permissions and
limitations under the License.
-->
-This topic describes how Geode processes set their CLASSPATH.
+This topic describes how <%=vars.product_name%> processes set their CLASSPATH.
-To simplify CLASSPATH environment settings, Geode has organized all application libraries required by Geode processes into `*-dependencies.jar` files. All dependency JAR files are located in the `path_to_product/lib` directory. When starting a server or locator process using `gfsh`, the required application JAR files are automatically loaded into the process's CLASSPATH for you.
+To simplify CLASSPATH environment settings, <%=vars.product_name%> has organized all application libraries required by <%=vars.product_name%> processes into `*-dependencies.jar` files. All dependency JAR files are located in the `path_to_product/lib` directory. When starting a server or locator process using `gfsh`, the required application JAR files are automatically loaded into the process's CLASSPATH for you.
**Note:**
-To embed Geode in your application, add `path_to_product/lib/geode-dependencies.jar` to your CLASSPATH.
+To embed <%=vars.product_name%> in your application, add `path_to_product/lib/geode-dependencies.jar` to your CLASSPATH.
-The following table lists the dependency JAR files associated with various Geode processes:
+The following table lists the dependency JAR files associated with various <%=vars.product_name%> processes:
<table>
<colgroup>
@@ -35,7 +35,7 @@ The following table lists the dependency JAR files associated with various Geode
</colgroup>
<thead>
<tr class="header">
-<th>Geode Process</th>
+<th><%=vars.product_name%> Process</th>
<th>Associated JAR Files</th>
</tr>
</thead>
@@ -49,7 +49,7 @@ The following table lists the dependency JAR files associated with various Geode
<td>geode-dependencies.jar
<div class="note note">
Note:
-<p>Use this library for all standalone or embedded Geode processes (including Java clients) that host cache data.</p>
+<p>Use this library for all standalone or embedded <%=vars.product_name%> processes (including Java clients) that host cache data.</p>
</div></td>
</tr>
</tbody>
@@ -57,7 +57,7 @@ Note:
## Modifying the CLASSPATH in gfsh-Managed Processes
-There are two options for updating the CLASSPATH of Geode server and locator processes that are started on the gfsh command line.
+There are two options for updating the CLASSPATH of <%=vars.product_name%> server and locator processes that are started on the gfsh command line.
**Option 1:** Specify the `--classpath` parameter upon process startup. For example, to modify the CLASSPATH of a locator:
@@ -71,7 +71,7 @@ And to modify the CLASSPATH of a server:
gfsh> start server --name=server1 --classpath=/path/to/applications/classes.jar
```
-Application classes supplied as arguments to the `--classpath` option are *prepended* to the server or locator's CLASSPATH, beginning in second position. The first entry in the CLASSPATH is reserved for the core Geode jar file, for security reasons.
+Application classes supplied as arguments to the `--classpath` option are *prepended* to the server or locator's CLASSPATH, beginning in second position. The first entry in the CLASSPATH is reserved for the core <%=vars.product_name%> jar file, for security reasons.
**Option 2:** Define the CLASSPATH environment variable in your OS environment. Then, specify the `--include-system-classpath` parameter upon process startup. For example:
@@ -89,9 +89,9 @@ This option *appends* the contents of the system CLASSPATH environment variable
## Setting the CLASSPATH for Applications and Standalone Java Processes
-If you are starting a Geode process programmatically (standalone or embedded), we recommend that you specify the CLASSPATH upon program execution using the `java -classpath` or `java -cp` command-line option. This method is preferred to setting the CLASSPATH as an environment variable since it allows you to set the value individually for each application without affecting other applications and without other applications modifying its value.
+If you are starting a <%=vars.product_name%> process programmatically (standalone or embedded), we recommend that you specify the CLASSPATH upon program execution using the `java -classpath` or `java -cp` command-line option. This method is preferred to setting the CLASSPATH as an environment variable since it allows you to set the value individually for each application without affecting other applications and without other applications modifying its value.
-For example, to start up a Geode locator process using the LocatorLauncher API, you can execute the following on the command line:
+For example, to start up a <%=vars.product_name%> locator process using the LocatorLauncher API, you can execute the following on the command line:
``` pre
prompt# java -cp "path_to_product/lib/geode-dependencies.jar"
@@ -99,7 +99,7 @@ org.apache.geode.distributed.LocatorLauncher start locator1
<locator-launcher-options>
```
-To start up a Geode server process using the ServerLauncher API:
+To start up a <%=vars.product_name%> server process using the ServerLauncher API:
``` pre
prompt# java -cp "path_to_product/lib/geode-dependencies.jar:/path/to/your/applications/classes.jar"
@@ -107,7 +107,7 @@ org.apache.geode.distributed.ServerLauncher start server1
<server-launcher-options>
```
-Note that in addition to the `*-dependencies.jar` file associated with the process, you must also specify any custom application JARs that you wish to access in your Geode process. For example, if you are planning on using a customized compressor on your regions, you should specify the application JAR that contains the compressor application you wish to use.
+Note that in addition to the `*-dependencies.jar` file associated with the process, you must also specify any custom application JARs that you wish to access in your <%=vars.product_name%> process. For example, if you are planning on using a customized compressor on your regions, you should specify the application JAR that contains the compressor application you wish to use.
To start up an application with an embedded cache:
@@ -117,6 +117,6 @@ com.mycompany.package.ApplicationWithEmbeddedCache
```
**Note:**
-Another method for updating the CLASSPATH of a server process with your own applications is to use the `gfsh deploy` command. Deploying application JAR files will automatically update the CLASSPATH of all members that are targeted for deployment. See [Deploying Application JARs to Apache Geode Members](../configuring/cluster_config/deploying_application_jars.html#concept_4436C021FB934EC4A330D27BD026602C) for more details.
+Another method for updating the CLASSPATH of a server process with your own applications is to use the `gfsh deploy` command. Deploying application JAR files will automatically update the CLASSPATH of all members that are targeted for deployment. See [Deploying Application JARs to <%=vars.product_name_long%> Members](../configuring/cluster_config/deploying_application_jars.html#concept_4436C021FB934EC4A330D27BD026602C) for more details.
http://git-wip-us.apache.org/repos/asf/geode/blob/0e6bf546/geode-docs/getting_started/system_requirements/host_machine.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/getting_started/system_requirements/host_machine.html.md.erb b/geode-docs/getting_started/system_requirements/host_machine.html.md.erb
index ce00704..787e896 100644
--- a/geode-docs/getting_started/system_requirements/host_machine.html.md.erb
+++ b/geode-docs/getting_started/system_requirements/host_machine.html.md.erb
@@ -19,10 +19,10 @@ See the License for the specific language governing permissions and
limitations under the License.
-->
-Host machines must meet a set of requirements for Apache Geode.
+Host machines must meet a set of requirements for <%=vars.product_name_long%>.
<a id="system_requirements__section_1E1F206FBC8B4A898A449E0699907A7A"></a>
-Each machine that will run Apache Geode must meet the following requirements:
+Each machine that will run <%=vars.product_name_long%> must meet the following requirements:
- Java SE Development Kit 8 or a more recent version.
- A system clock set to the correct time and a time synchronization service such as Network Time Protocol (NTP). Correct time stamps permit the following activities:
http://git-wip-us.apache.org/repos/asf/geode/blob/0e6bf546/geode-docs/getting_started/uninstall_geode.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/getting_started/uninstall_geode.html.md.erb b/geode-docs/getting_started/uninstall_geode.html.md.erb
index e5cac8a..d56e932 100644
--- a/geode-docs/getting_started/uninstall_geode.html.md.erb
+++ b/geode-docs/getting_started/uninstall_geode.html.md.erb
@@ -19,8 +19,8 @@ See the License for the specific language governing permissions and
limitations under the License.
-->
-This section describes how to remove Geode.
+This section describes how to remove <%=vars.product_name%>.
-Shut down any running Geode processes and then remove the entire directory tree. No additional system modifications or modification of Windows registry entries are needed.
+Shut down any running <%=vars.product_name%> processes and then remove the entire directory tree. No additional system modifications or modification of Windows registry entries are needed.