You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@geode.apache.org by km...@apache.org on 2016/10/14 22:17:24 UTC
[26/94] [abbrv] [partial] incubator-geode git commit: GEODE-1952
Consolidated docs under a single geode-docs directory
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/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
new file mode 100644
index 0000000..05c946c
--- /dev/null
+++ b/geode-docs/getting_started/book_intro.html.md.erb
@@ -0,0 +1,23 @@
+---
+title: Getting Started with Apache Geode
+---
+
+A tutorial demonstrates features, and a main features section describes key functionality.
+
+- **[About Apache Geode](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.
+
+- **[Main Features of Apache Geode](product_intro.html)**
+
+ This section summarizes the main features and key functionality of Apache Geode.
+
+- **[Prerequisites and Installation Instructions](../prereq_and_install.html)**
+
+ Each host of Apache Geode 1.0.0-incubating 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)**
+
+ Need a quick introduction to Apache Geode? Take this brief tour to try out basic features and functionality.
+
+
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/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
new file mode 100644
index 0000000..dca502c
--- /dev/null
+++ b/geode-docs/getting_started/geode_overview.html.md.erb
@@ -0,0 +1,20 @@
+---
+title: About Apache Geode
+---
+
+Apache Geode 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.
+
+## <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.
+
+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.
+
+<a id="concept_3B5E445B19884680900161BDF25E32C9__section_zrl_c41_mr"></a>
+
+For more information on product features, see [Main Features of Apache Geode](product_intro.html).
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/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
new file mode 100644
index 0000000..22936c7
--- /dev/null
+++ b/geode-docs/getting_started/installation/install_standalone.html.md.erb
@@ -0,0 +1,121 @@
+---
+title: How to Install
+---
+
+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 on Unix
+
+1. Set the JAVA\_HOME environment variable.
+
+ ``` pre
+ JAVA_HOME=/usr/java/jdk1.8.0_60
+ export JAVA_HOME
+ ```
+
+2. Download the project source from the Releases page found at [http://geode.incubator.apache.org](http://geode.incubator.apache.org/), and unpack the source code.
+3. Within the directory containing the unpacked source code, build without tests:
+
+ ``` pre
+ $ ./gradlew build -Dskip.tests=true
+ ```
+
+ Or, build with the tests:
+
+ ``` pre
+ $ ./gradlew build
+ ```
+
+4. Verify the installation by invoking `gfsh` to print version information and exit. On Linux/Unix platforms, the version will be similar to:
+
+ ``` pre
+ $ cd geode-assembly/build/install/apache-geode
+ $ bin/gfsh version
+ v1.0.0-incubating
+ ```
+
+## Build from Source on Windows
+
+1. Set the JAVA\_HOME environment variable. For example:
+
+ ``` pre
+ $ set JAVA_HOME="C:\Program Files\Java\jdk1.8.0_60"
+ ```
+
+2. Install Gradle, version 2.3 or a more recent version.
+3. Download the project source from the Releases page found at [http://geode.incubator.apache.org](http://geode.incubator.apache.org/), and unpack the source code.
+4. Within the folder containing the unpacked source code, build without the tests:
+
+ ``` pre
+ $ gradle build -Dskip.tests=true
+ ```
+
+ Or, build with the tests:
+
+ ``` pre
+ $ gradle build
+ ```
+
+5. Verify the installation by invoking `gfsh` to print version information and exit.
+
+ ``` pre
+ $ cd geode-assembly\build\install\apache-geode\bin
+ $ gfsh.bat version
+ v1.0.0-incubating
+ ```
+
+## <a id="concept_0129F6A1D0EB42C4A3D24861AF2C5425__section_D3326496B2BB47A7AB0CFC1A5E266842" class="no-quick-link"></a>Install Binaries from .zip or .tar File
+
+1. Download the .zip or .tar file from the Releases page found at [http://geode.incubator.apache.org](http://geode.incubator.apache.org/).
+2. Unzip the .zip file or expand the .tar file, where `path_to_product` is an absolute path, and the file name will vary due to the version number. For the .zip format:
+
+ ``` pre
+ $ unzip apache-geode-1.0.0-incubating.zip -d path_to_product
+ ```
+
+ For the .tar format:
+
+ ``` pre
+ $ tar -xvf apache-geode-1.0.0-incubating.tar -C path_to_product
+ ```
+
+3. Set the JAVA\_HOME environment variable. On Linux/Unix platforms:
+
+ ``` pre
+ JAVA_HOME=/usr/java/jdk1.8.0_60
+ export JAVA_HOME
+ ```
+
+ On Windows platforms:
+
+ ``` pre
+ 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:
+
+ ``` pre
+ PATH=$PATH:$JAVA_HOME/bin:path_to_product/bin
+ export PATH
+ ```
+
+ On Windows platforms:
+
+ ``` pre
+ 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:
+
+ ``` pre
+ $ gfsh version
+ v1.0.0-incubating
+ ```
+
+ For more detailed version information such as the date of the build, build number and JDK version being used, invoke:
+
+ ``` pre
+ $ gfsh version --full
+ ```
+
+
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/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
new file mode 100644
index 0000000..c5ccb60
--- /dev/null
+++ b/geode-docs/getting_started/product_intro.html.md.erb
@@ -0,0 +1,84 @@
+---
+title: Main Features of Apache Geode
+---
+
+This section summarizes the main features and key functionality of Apache Geode.
+
+- [High Read-and-Write Throughput](product_intro.html#concept_3B5E445B19884680900161BDF25E32C9__section_CF0E3E5C4F884374B8F2F536DD2A375C)
+- [Low and Predictable Latency](product_intro.html#concept_3B5E445B19884680900161BDF25E32C9__section_9C5D669B583646F1B817284EB494DDA7)
+- [High Scalability](product_intro.html#concept_3B5E445B19884680900161BDF25E32C9__section_EF7A73D35D1241289C9CA19EDDEBE959)
+- [Continuous Availability](product_intro.html#concept_3B5E445B19884680900161BDF25E32C9__section_CEB4ABFF83054AF6A47EA2FA09C240B1)
+- [Reliable Event Notifications](product_intro.html#concept_3B5E445B19884680900161BDF25E32C9__section_86D2B8CC346349F3913209AF87648A02)
+- [Parallelized Application Behavior on Data Stores](product_intro.html#concept_3B5E445B19884680900161BDF25E32C9__section_A65B5F0DE8BF4AA6AFF16E3A75D4E0AD)
+- [Shared-Nothing Disk Persistence](product_intro.html#concept_3B5E445B19884680900161BDF25E32C9__section_97CABBFF553647F6BBBC40AA7AF6D4C7)
+- [Reduced Cost of Ownership](product_intro.html#concept_3B5E445B19884680900161BDF25E32C9__section_FCB2640F1BED4692A93F9300A41CE70D)
+- [Single-Hop Capability for Client/Server](product_intro.html#concept_3B5E445B19884680900161BDF25E32C9__section_92A444D4B422434EBD5F81D11F32C1C7)
+- [Client/Server Security](product_intro.html#concept_3B5E445B19884680900161BDF25E32C9__section_577F601BC9854AA6B53CD3440F9B9A6A)
+- [Multisite Data Distribution](product_intro.html#concept_3B5E445B19884680900161BDF25E32C9__section_091A306900D7402CAE5A46B5F9BFD612)
+- [Continuous Querying](product_intro.html#concept_3B5E445B19884680900161BDF25E32C9__section_FF4C3B6E26104C4D93186F6FFE22B321)
+
+## <a id="concept_3B5E445B19884680900161BDF25E32C9__section_CF0E3E5C4F884374B8F2F536DD2A375C" class="no-quick-link"></a>High Read-and-Write Throughput
+
+Geode uses concurrent main-memory data structures and a highly optimized distribution infrastructure to provide read-and-write throughput. Applications can make copies of data dynamically in memory through synchronous or asynchronous replication for high read throughput or partition the data across many Geode system members to achieve high read-and-write throughput. Data partitioning doubles the aggregate throughput if the data access is fairly balanced across the entire data set. Linear increase in throughput is limited only by the backbone network capacity.
+
+## <a id="concept_3B5E445B19884680900161BDF25E32C9__section_9C5D669B583646F1B817284EB494DDA7" class="no-quick-link"></a>Low and Predictable Latency
+
+Geode's optimized caching layer minimizes context switches between threads and processes. It manages data in highly concurrent structures to minimize contention points. Communication to peer members is synchronous if the receivers can keep up, which keeps the latency for data distribution to a minimum. Servers manage object graphs in serialized form to reduce the strain on the garbage collector.
+
+Geode partitions subscription management (interest registration and continuous queries) across server data stores, ensuring that a subscription is processed only once for all interested clients. The resulting improvements in CPU use and bandwidth utilization improve throughput and reduce latency for client subscriptions.
+
+## <a id="concept_3B5E445B19884680900161BDF25E32C9__section_EF7A73D35D1241289C9CA19EDDEBE959" class="no-quick-link"></a>High Scalability
+
+Geode achieves scalability through dynamic partitioning of data across many members and spreading the data load uniformly across the servers. For "hot" data, you can configure the system to expand dynamically to create more copies of the data. You can also provision application behavior to run in a distributed manner in close proximity to the data it needs.
+
+If you need to support high and unpredictable bursts of concurrent client load, you can increase the number of servers managing the data and distribute the data and behavior across them to provide uniform and predictable response times. Clients are continuously load balanced to the server farm based on continuous feedback from the servers on their load conditions. With data partitioned and replicated across servers, clients can dynamically move to different servers to uniformly load the servers and deliver the best response times.
+
+You can also improve scalability by implementing asynchronous "write behind" of data changes to external data stores, like a database. Geode avoids a bottleneck by queuing all updates in order and redundantly. You can also conflate updates and propagate them in batch to the database.
+
+## <a id="concept_3B5E445B19884680900161BDF25E32C9__section_CEB4ABFF83054AF6A47EA2FA09C240B1" class="no-quick-link"></a>Continuous Availability
+
+In addition to guaranteed consistent copies of data in memory, applications can persist data to disk on one or more Geode members synchronously or asynchronously by using Geode's "shared nothing disk architecture." All asynchronous events (store-forward events) are redundantly managed in at least two members such that if one server fails, the redundant one takes over. All clients connect to logical servers, and the client fails over automatically to alternate servers in a group during failures or when servers become unresponsive.
+
+## <a id="concept_3B5E445B19884680900161BDF25E32C9__section_86D2B8CC346349F3913209AF87648A02" class="no-quick-link"></a>Reliable Event Notifications
+
+Publish/subscribe systems offer a data-distribution service where new events are published into the system and routed to all interested subscribers in a reliable manner. Traditional messaging platforms focus on message delivery, but often the receiving applications need access to related data before they can process the event. This requires them to access a standard database when the event is delivered, limiting the subscriber by the speed of the database.
+
+Geode offers data and events through a single system. Data is managed as objects in one or more distributed data regions, similar to tables in a database. Applications simply insert, update, or delete objects in data regions, and the platform delivers the object changes to the subscribers. The subscriber receiving the event has direct access to the related data in local memory or can fetch the data from one of the other members through a single hop.
+
+## <a id="concept_3B5E445B19884680900161BDF25E32C9__section_A65B5F0DE8BF4AA6AFF16E3A75D4E0AD" class="no-quick-link"></a>Parallelized Application Behavior on Data Stores
+
+You can execute application business logic in parallel on the Geode members. Geode's data-aware function-execution service permits execution of arbitrary, data-dependent application functions on the members where the data is partitioned for locality of reference and scale.
+
+By colocating the relevant data and parallelizing the calculation, you increase overall throughput. The calculation latency is inversely proportional to the number of members on which it can be parallelized.
+
+The fundamental premise is to route the function transparently to the application that carries the data subset required by the function and to avoid moving data around on the network. Application function can be executed on only one member, in parallel on a subset of members, or in parallel across all members. This programming model is similar to the popular Map-Reduce model from Google. Data-aware function routing is most appropriate for applications that require iteration over multiple data items (such as a query or custom aggregation function).
+
+## <a id="concept_3B5E445B19884680900161BDF25E32C9__section_97CABBFF553647F6BBBC40AA7AF6D4C7" class="no-quick-link"></a>Shared-Nothing Disk Persistence
+
+Each Geode system member manages data on disk files independent of other members. Failures in disks or cache failures in one member do not affect the ability of another cache instance to operate safely on its disk files. This "shared nothing" persistence architecture allows applications to be configured such that different classes of data are persisted on different members across the system, dramatically increasing the overall throughput of the application even when disk persistence is configured for application objects.
+
+Unlike a traditional database system, Geode does not manage data and transaction logs in separate files. All data updates are appended to files that are similar to transactional logs of traditional databases. You can avoid disk-seek times if the disk is not concurrently used by other processes, and the only cost incurred is the rotational latency.
+
+## <a id="concept_3B5E445B19884680900161BDF25E32C9__section_FCB2640F1BED4692A93F9300A41CE70D" class="no-quick-link"></a>Reduced Cost of Ownership
+
+You can configure caching in tiers. The client application process can host a cache locally (in memory and overflow to disk) and delegate to a cache server farm on misses. Even a 30 percent hit ratio on the local cache translates to significant savings in costs. The total cost associated with every single transaction comes from the CPU cycles spent, the network cost, the access to the database, and intangible costs associated with database maintenance. By managing the data as application objects, you avoid the additional cost (CPU cycles) associated with mapping SQL rows to objects.
+
+## <a id="concept_3B5E445B19884680900161BDF25E32C9__section_92A444D4B422434EBD5F81D11F32C1C7" class="no-quick-link"></a>Single-Hop Capability for Client/Server
+
+Clients can send individual data requests directly to the server holding the data key, avoiding multiple hops to locate data that is partitioned. Metadata in the client identifies the correct server. This feature improves performance and client access to partitioned regions in the server tier.
+
+## <a id="concept_3B5E445B19884680900161BDF25E32C9__section_577F601BC9854AA6B53CD3440F9B9A6A" class="no-quick-link"></a>Client/Server Security
+
+Geode supports running multiple, distinct users in client applications. This feature accommodates installations in which Geode clients are embedded in application servers and each application server supports data requests from many users. Each user may be authorized to access a small subset of data on the servers, as in a customer application where each customer can access only their own orders and shipments. Each user in the client connects to the server with its own set of credentials and has its own access authorization to the server cache.
+
+Client/server communication has increased security against replay attacks. The server sends the client a unique, random identifier with each response to be used in the next client request. Because of the identifier, even a repeated client operation call is sent as a unique request to the server.
+
+## <a id="concept_3B5E445B19884680900161BDF25E32C9__section_091A306900D7402CAE5A46B5F9BFD612" class="no-quick-link"></a>Multisite Data Distribution
+
+Scalability problems can result from data sites being spread out geographically across a wide-area network (WAN). GemFire offers a model to address these topologies, ranging from a single peer-to-peer cluster to reliable communications between data centers across the WAN. This model allows distributed systems to scale out in an unbounded and loosely coupled fashion without loss of performance, reliability or data consistency.
+
+At the core of this architecture is the gateway sender configuration used for distributing region events to a remote site. You can deploy gateway sender instances in parallel, which enables GemFire to increase the throughput for distributing region events across the WAN. You can also configure gateway sender queues for persistence and high availability to avoid data loss in the case of a member failure.
+
+## <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.
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/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
new file mode 100644
index 0000000..9a06d1f
--- /dev/null
+++ b/geode-docs/getting_started/querying_quick_reference.html.md.erb
@@ -0,0 +1,694 @@
+---
+title: Geode Querying FAQ and Examples
+---
+
+This topic answers some frequently asked questions on querying functionality. It provides examples to help you get started with Geode querying.
+
+<a id="reference_D5CE64F5FD6F4A808AEFB748C867189E__section_AFAD97A4BA2D45CF91ED1525A54DDFD6"></a>
+For additional information on Geode 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)
+- [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)
+- [Can I invoke a static method on an object in a query?](querying_quick_reference.html#reference_D5CE64F5FD6F4A808AEFB748C867189E__section_9221C29BC1FD49D7BBD26BB34D5BDEB8)
+- [How do I write a reusable query?](querying_quick_reference.html#reference_D5CE64F5FD6F4A808AEFB748C867189E__section_907DBBBA1AEC4570A15B3491B0A7DF0E)
+- [When should I create indexes to use in my queries?](querying_quick_reference.html#reference_D5CE64F5FD6F4A808AEFB748C867189E__section_3A9528E8E43140BAA0D5A1457CCAB2D2)
+- [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)
+- [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?
+
+To write and execute a query in Geode, you can use any of the following mechanisms. Sample query code follows.
+
+- Geode 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)**
+
+``` pre
+// Identify your query string.
+ String queryString = "SELECT * FROM /exampleRegion";
+
+ // Get QueryService from Cache.
+ QueryService queryService = cache.getQueryService();
+
+ // Create the Query Object.
+ Query query = queryService.newQuery(queryString);
+
+ // Execute Query locally. Returns results set.
+ SelectResults results = (SelectResults)query.execute();
+
+ // Find the Size of the ResultSet.
+ int size = results.size();
+
+ // Iterate through your ResultSet.
+ Portfolio p = (Portfolio)results.iterator().next(); /* Region containing Portfolio object. */
+```
+
+## <a id="reference_D5CE64F5FD6F4A808AEFB748C867189E__section_641D97CD874D4182961C85429ACA1B05" class="no-quick-link"></a>Can I see query string examples, listed by query type?
+
+The following example query strings use the `/exampleRegion` whose keys are the portfolio ID and whose values correspond to the summarized data shown in the following class definitions:
+
+``` pre
+class Portfolio implements DataSerializable {
+ int ID;
+ String type;
+ String status;
+ Map positions;
+}
+class Position implements DataSerializable {
+ String secId;
+ double mktValue;
+ double qty;
+}
+```
+
+**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.
+
+1. Select all active portfolios.
+
+ ``` pre
+ SELECT * FROM /exampleRegion WHERE status = 'active'
+ ```
+
+2. Select all portfolios whose status begins with 'activ'.
+
+ ``` pre
+ SELECT * FROM /exampleRegion p WHERE p.status LIKE 'activ%'
+ ```
+
+3. Select all portfolios whose ID is greater than 100.
+
+ ``` pre
+ SELECT * from /exampleRegion p WHERE p.ID > 100
+ ```
+
+**Using DISTINCT**
+
+Select distinct Objects from the region that satisfy the where clause condition of status = 'active'.
+
+``` pre
+SELECT DISTINCT * FROM /exampleRegion WHERE status = 'active'
+```
+
+**Aliases and Synonyms**
+
+In the query string, the path expressions (region and its objects) can be defined using an alias. This alias can be used or referred to in other places in the query.
+
+``` pre
+SELECT DISTINCT * FROM /exampleRegion p WHERE p.status = 'active'
+```
+
+``` pre
+SELECT p.ID, p.status FROM /exampleRegion p WHERE p.ID > 0
+```
+
+**Using the NOT Operator**
+
+See [Operators](../developing/query_additional/operators.html#operators) for a complete list of supported operators.
+
+``` pre
+SELECT DISTINCT * FROM /exampleRegion WHERE NOT (status = 'active') AND ID = 2
+```
+
+``` pre
+SELECT * FROM /exampleRegion WHERE NOT (ID IN SET(1,2))
+```
+
+**Using the AND and OR Operators**
+
+See [Operators](../developing/query_additional/operators.html#operators) for a complete list of supported operators.
+
+``` pre
+SELECT * FROM /exampleRegion WHERE ID > 4 AND ID < 9
+```
+
+``` pre
+SELECT * FROM /exampleRegion WHERE ID = 0 OR ID = 1
+```
+
+``` pre
+SELECT DISTINCT p.status FROM /exampleRegion p
+WHERE (p.createTime IN SET (10|) OR p.status IN SET ('active')) AND p.ID > 0
+```
+
+**Using not equal to**
+
+``` pre
+SELECT * FROM /exampleRegion portfolio WHERE portfolio.ID <> 2
+```
+
+``` pre
+SELECT * FROM /exampleRegion portfolio WHERE portfolio.ID != 2
+```
+
+**Projection attribute example**
+
+``` pre
+SELECT p.get('account') FROM /exampleRegion p
+```
+
+**Querying nested collections**
+
+The following query uses Positions of type HashMap.
+
+``` pre
+SELECT p, pos FROM /exampleRegion p, p.positions.values pos WHERE pos.secId = 'VMW'
+```
+
+**Using LIMIT**
+
+``` pre
+SELECT * FROM /exampleRegion p WHERE p.ID > 0 LIMIT 2
+```
+
+**Using COUNT**
+
+See [COUNT](../developing/query_select/the_select_statement.html#concept_85AE7D6B1E2941ED8BD2A8310A81753E__section_B2CBA00EB83F463DAF4769D7859C64C8) for more information.
+
+``` pre
+SELECT COUNT(*) FROM /exampleRegion WHERE ID > 0
+```
+
+``` pre
+SELECT COUNT(*) FROM /exampleRegion WHERE ID > 0 LIMIT 50
+```
+
+``` pre
+SELECT COUNT(*) FROM /exampleRegion WHERE ID > 0 AND status LIKE 'act%'
+```
+
+``` pre
+SELECT COUNT(*) FROM /exampleRegion WHERE ID IN SET(1,2,3,4,5)
+```
+
+``` pre
+SELECT COUNT(*) FROM /exampleRegion p, p.positions.values pos
+WHERE p.ID > 0 AND pos.secId 'IBM'
+```
+
+``` pre
+SELECT DISTINCT COUNT(*) FROM /exampleRegion p, p.positions.values pos
+WHERE p.ID > 0 OR p.status = 'active' OR pos.secId OR pos.secId = 'IBM'
+```
+
+**Using LIKE**
+
+``` pre
+SELECT * FROM /exampleRegion ps WHERE ps.pkid LIKE '_bc'
+```
+
+``` pre
+SELECT * FROM /exampleRegion ps WHERE ps.status LIKE '_b_' OR ps.pkid = '2'
+```
+
+``` pre
+SELECT * FROM /exampleRegion ps WHERE ps.status LIKE '%b%
+```
+
+**Using Region Entry Keys and Values**
+
+``` pre
+SELECT * FROM /exampleRegion.keys k WHERE k.ID = 1
+```
+
+``` pre
+SELECT entry.value FROM /exampleRegion.entries entry WHERE entry.key = '1'
+```
+
+``` pre
+SELECT key, positions FROM /exampleRegion.entrySet, value.positions.values positions
+WHERE positions.mktValue >= 25.00
+```
+
+``` pre
+SELECT DISTINCT entry.value FROM /exampleRegion.entries entry WHERE entry.key = '1'
+```
+
+``` pre
+SELECT * FROM /exampleRegion.entries entry WHERE entry.value.ID > 1
+```
+
+``` pre
+SELECT * FROM /exampleRegion.keySet key WHERE key = '1'
+```
+
+``` pre
+SELECT * FROM /exampleRegion.values portfolio
+WHERE portfolio.status = 'active'
+```
+
+**Nested Queries**
+
+``` pre
+IMPORT "query".Portfolio;
+SELECT * FROM /exampleRegion, (SELECT DISTINCT * FROM /exampleRegion p TYPE Portfolio, p.positions
+WHERE value!=null)
+```
+
+``` pre
+SELECT DISTINCT * FROM (SELECT DISTINCT * FROM /exampleRegion portfolios, positions pos)
+WHERE pos.value.secId = 'IBM'
+```
+
+``` pre
+SELECT * FROM /exampleRegion portfolio
+WHERE portfolio.ID IN (SELECT p2.ID FROM /exampleRegion2 p2 WHERE p2.ID > 1)
+```
+
+``` pre
+SELECT DISTINCT * FROM /exampleRegion p, (SELECT DISTINCT pos
+FROM /exampleRegion x, x.positions.values pos WHERE x.ID = p.ID ) AS itrX
+```
+
+**Query the results of a FROM clause expression**
+
+``` pre
+SELECT DISTINCT * FROM (SELECT DISTINCT * FROM /Portfolios ptf, positions pos) p
+WHERE p.get('pos').value.secId = 'IBM'
+```
+
+**Hash Map Query**
+
+Query using a hashmap. In the following examples, 'version' is one of the keys in the hashmap.
+
+``` pre
+SELECT * FROM /exampleRegion p WHERE p['version'] = '1.0'
+```
+
+``` pre
+SELECT entry.key, entry.value FROM /exampleRegion.entries entry
+WHERE entry.value['version'] = '100'
+```
+
+**Map example where "map" is a nested HashMap object**
+
+``` pre
+SELECT DISTINCT * FROM /exampleRegion p WHERE p.portfolios['key2'] >= 3
+```
+
+**Example Queries that Fetch Array Values**
+
+``` pre
+SELECT * FROM /exampleRegion p WHERE p.names[0] = 'aaa'
+```
+
+``` pre
+SELECT * FROM /exampleRegion p WHERE p.collectionHolderMap.get('1').arr[0] = '0'
+```
+
+**Using ORDER BY (and ORDER BY with LIMIT)**
+
+You must use the DISTINCT keyword with ORDER BY queries.
+
+``` pre
+SELECT DISTINCT * FROM /exampleRegion WHERE ID < 101 ORDER BY ID
+```
+
+``` pre
+SELECT DISTINCT * FROM /exampleRegion WHERE ID < 101 ORDER BY ID asc
+```
+
+``` pre
+SELECT DISTINCT * FROM /exampleRegion WHERE ID < 101 ORDER BY ID desc
+```
+
+``` pre
+SELECT DISTINCT key.ID, key.status AS st FROM /exampleRegion.keys key
+WHERE key.status = 'inactive' ORDER BY key.status desc, key.ID LIMIT 1
+```
+
+``` pre
+SELECT DISTINCT * FROM /exampleRegion p ORDER BY p.getP1().secId, p.ID dec, p.ID LIMIT 9
+```
+
+``` pre
+SELECT DISTINCT * FROM /exampleRegion p ORDER BY p.ID, val.secId LIMIT 1
+```
+
+``` pre
+SELECT DISTINCT e.key FROM /exampleRegion.entrySet e ORDER BY e.key.ID desc, e.key.pkid desc
+```
+
+``` pre
+SELECT DISTINCT p.names[1] FROM /exampleRegion p ORDER BY p.names[1]
+```
+
+**Join Queries**
+
+``` pre
+SELECT * FROM /exampleRegion portfolio1, /exampleRegion2 portfolio2
+WHERE portfolio1.status = portfolio2.status
+```
+
+``` pre
+SELECT portfolio1.ID, portfolio2.status FROM /exampleRegion portfolio1, /exampleRegion2 portfolio2
+WHERE portfolio1.status = portfolio2.status
+```
+
+``` pre
+SELECT * FROM /exampleRegion portfolio1, portfolio1.positions.values positions1,
+/exampleRegion2 portfolio2, portfolio2.positions.values positions2 WHERE positions1.secId = positions1.secId
+```
+
+``` pre
+SELECT * FROM /exampleRegion portfolio1, portfolio1.positions.values positions1,
+/exampleRegion2 portfolio2, portfolio2.positions.values positions2 WHERE portfolio1.ID = 1
+AND positions1.secId = positions1.secId
+```
+
+``` pre
+SELECT DISTINCT a, b.price FROM /exampleRegoin1 a, /exampleRegion2 b WHERE a.price = b.price
+```
+
+**Using AS**
+
+``` pre
+SELECT * FROM /exampleRegion p, p.positions.values AS pos WHERE pos.secId != '1'
+```
+
+**Using TRUE**
+
+``` pre
+SELECT DISTINCT * FROM /Portfolios WHERE TRUE
+```
+
+**Using IN and SET**
+
+See also [IN and SET](../developing/query_select/the_where_clause.html#the_where_clause__section_AC12146509F141378E493078540950C7).
+
+``` pre
+SELECT * FROM /exampleRegion portfolio WHERE portfolio.ID IN SET(1, 2)
+```
+
+``` pre
+SELECT * FROM /exampleRegion portfolio, portfolio.positions.values positions
+WHERE portfolio.Pk IN SET ('1', '2') AND positions.secId = '1'
+```
+
+``` pre
+SELECT * FROM /exampleRegion portfolio, portfolio.positions.values positions
+WHERE portfolio.Pk IN SET ('1', '2') OR positions.secId IN SET ('1', '2', '3')
+```
+
+``` pre
+SELECT * FROM /exampleRegion portfolio, portfolio.positions.values positions
+WHERE portfolio.Pk IN SET ('1', '2') OR positions.secId IN SET ('1', '2', '3')
+AND portfolio.status = 'active'
+```
+
+**Querying for Set values**
+
+In the following query, sp is of type Set.
+
+``` pre
+SELECT * FROM /exampleRegion WHERE sp = set('20', '21', '22')
+```
+
+If the Set (sp) only contains '20' and '21', then the query will evaluate to false. The query compares the two sets and looks for the presence of elements in both sets.
+
+For other collection types like list (sp is of type List), the query can be written as follows:
+
+``` pre
+SELECT * FROM /exampleRegion WHERE sp.containsAll(set('20', '21', '22'))
+```
+
+**Invoking Methods on Objects**
+
+See [Method Invocations](../developing/query_select/the_where_clause.html#the_where_clause__section_D2F8D17B52B04895B672E2FCD675A676) for more information.
+
+``` pre
+SELECT * FROM /exampleRegion p WHERE p.length > 1
+```
+
+``` pre
+SELECT DISTINCT * FROM /exampleRegion p WHERE p.positions.size >= 2
+```
+
+``` pre
+SELECT DISTINCT * FROM /exampleRegion p WHERE p.positions.isEmpty
+```
+
+``` pre
+SELECT DISTINCT * FROM /exampleRegion p WHERE p.name.startsWith('Bo')
+```
+
+**Using Query-Level Debugging**
+
+To set debugging on the query level, add the **<trace>** keyword before the query. (If you are using an IMPORT statement, include it before the IMPORT).
+
+``` pre
+<trace>
+SELECT * from /exampleRegion, positions.values TYPE myclass
+```
+
+**Using Reserved Words in Queries**
+
+To access any method, attribute, or named object that has the same name as a query language reserved word, enclose the name within double quotation marks.
+
+``` pre
+SELECT * FROM /exampleRegion WHERE status = 'active' AND "type" = 'XYZ'
+```
+
+``` pre
+SELECT DISTINCT "type" FROM /exampleRegion WHERE status = 'active'
+```
+
+**Using IMPORT**
+
+In the case where the same class name resides in two different namescopes (packages), there needs to be a means of referring to different classes of the same name. The IMPORT statement is used to establish a namescope for a class in a query.
+
+``` pre
+IMPORT package.Position;
+SELECT DISTINCT * FROM /exampleRegion, positions.values positions TYPE Position WHERE positions.mktValue >= 25.00
+```
+
+**Using TYPE**
+
+Specifying object type helps the query engine to process the query at optimal speed. Apart from specifying the object types during configuration (using key-constraint and value-constraint), type can be explicitly specified in the query string.
+
+``` pre
+SELECT DISTINCT * FROM /exampleRegion, positions.values positions TYPE Position WHERE positions.mktValue >= 25.00
+```
+
+**Using ELEMENT**
+
+Using ELEMENT(expr) extracts a single element from a collection or array. This function throws a `FunctionDomainException` if the argument is not a collection or array with exactly one element.
+
+``` pre
+ELEMENT(SELECT DISTINCT * FROM /exampleRegion WHERE id = 'XYZ-1').status = 'active'
+```
+
+## <a id="reference_D5CE64F5FD6F4A808AEFB748C867189E__section_5383407F9D004D4EB4E695252EBA1EF0" class="no-quick-link"></a>Which APIs should I use to write my queries?
+
+If you are querying a Java application\u2019s local cache or querying other members, use [org.apache.geode.cache.Cache.getQueryService](/releases/latest/javadoc/org/apache/geode/cache/query/QueryService.html).
+
+If you are writing a Java client to server query, use [org.apache.geode.cache.client.Pool.getQueryService](/releases/latest/javadoc/org/apache/geode/cache/client/Pool.html).
+
+If you are writing a native client to server query, use the [.NET API](/releases/latest/net_api/DotNetDocs/Index.html) or the [C++ API](/releases/latest/cpp_api/cppdocs/index.html).
+
+## <a id="reference_D5CE64F5FD6F4A808AEFB748C867189E__section_3E6E4B33D57846008EF4404D2B687597" class="no-quick-link"></a>How do I invoke an object's method in a query?
+
+To use a method in a query, use the attribute name that maps to the public method you want to invoke. For example:
+
+``` pre
+/*valid method invocation*/
+SELECT DISTINCT * FROM /exampleRegion p WHERE p.positions.size >= 2 - maps to positions.size()
+```
+
+## <a id="reference_D5CE64F5FD6F4A808AEFB748C867189E__section_9221C29BC1FD49D7BBD26BB34D5BDEB8" class="no-quick-link"></a>Can I invoke a static method on an object in a query?
+
+No, you cannot invoke a static method on an object. For example, the following query is invalid.
+
+``` pre
+/*invalid method invocation*/
+SELECT DISTINCT * FROM /exampleRegion WHERE aDay = Day.Wednesday
+```
+
+To work around this limitation, write a reusable query that uses a query bind parameter to invoke the static method. Then at query run time, set the parameter to the static method invocation (`Day.Wednesday`). For example:
+
+``` pre
+SELECT DISTINCT * FROM /exampleRegion WHERE aDay = $1
+```
+
+## <a id="reference_D5CE64F5FD6F4A808AEFB748C867189E__section_907DBBBA1AEC4570A15B3491B0A7DF0E" class="no-quick-link"></a>How do I write a reusable query?
+
+Using query APIs, you can set query bind parameters that are passed values at query run time. For example:
+
+``` pre
+// specify the query string
+ String queryString = "SELECT DISTINCT * FROM /exampleRegion p WHERE p.status = $1";
+
+QueryService queryService = cache.getQueryService();
+Query query = queryService.newQuery(queryString);
+
+// set a query bind parameter
+Object[] params = new Object[1];
+params[0] = "active";
+
+// Execute the query locally. It returns the results set.
+SelectResults results = (SelectResults) query.execute(params);
+
+// use the results of the query; this example only looks at the size
+ int size = results.size();
+```
+
+If you use a query bind parameter in place of a region path in your path expression, the parameter value must reference a collection (and not a String such as the name of the region path.)
+
+See [Using Query Bind Parameters](../developing/query_additional/using_query_bind_parameters.html#concept_173E775FE46B47DF9D7D1E40680D34DF) for more details.
+
+## <a id="reference_D5CE64F5FD6F4A808AEFB748C867189E__section_3A9528E8E43140BAA0D5A1457CCAB2D2" class="no-quick-link"></a>When should I create indexes to use in my queries?
+
+Determine whether your query\u2019s performance will benefit from an index. For example, in the following query, an index on pkid can speed up the query.
+
+``` pre
+SELECT DISTINCT * FROM /exampleRegion portfolio WHERE portfolio.pkid = '123'
+```
+
+## <a id="reference_D5CE64F5FD6F4A808AEFB748C867189E__section_76CDCCFBDB134A339DBE556C28D48F11" class="no-quick-link"></a>How do I create an index?
+
+An index can be created programmatically using APIs or by using xml. Here are two examples:
+
+**Sample Code**
+
+``` pre
+QueryService qs = cache.getQueryService();
+ qs.createIndex("myIndex", "status", "/exampleRegion");
+ qs.createKeyIndex("myKeyIndex", "id", "exampleRegion");
+```
+
+For more information on using this API, see the [GemFire JavaDocs](/releases/latest/javadoc/index.html).
+
+**Sample XML**
+
+``` pre
+<region name="portfolios">
+ <region-attributes . . . >
+ </region-attributes>
+ <index name="myIndex">
+ <functional from-clause="/exampleRegion"
+ expression="status"/>
+ </index>
+ <index name="myKeyIndex">
+ <primary-key field="id"/>
+ </index>
+ <entry>
+```
+
+For more details on indexes, see [Working with Indexes](../developing/query_index/query_index.html).
+
+## <a id="reference_D5CE64F5FD6F4A808AEFB748C867189E__section_30D8C9A5472E4768AB7A0D598C9A496E" class="no-quick-link"></a>Can I create indexes on overflow regions?
+
+You can create indexes on overflow regions, but you are subject to some limitations. For example, the data contained in the index itself cannot be overflowed to disk. See [Using Indexes with Overflow Regions](../developing/query_index/indexes_with_overflow_regions.html#concept_87BE7DB32C714EB0BF7532AF93569328) for more information.
+
+## <a id="reference_D5CE64F5FD6F4A808AEFB748C867189E__section_EDD17817450C4FC0B510CD87DB2FCD16" class="no-quick-link"></a>Can I query a partitioned region? Can I perform a join query on a partitioned region?
+
+You can query partitioned regions, but there are some limitations. You cannot perform join queries on partitioned regions, however you can perform equi-join queries on colocated partitioned regions by executing a function on a local data set.
+
+For a full list of restrictions, see [Partitioned Region Query Restrictions](../developing/query_additional/partitioned_region_query_restrictions.html#concept_5353476380D44CC1A7F586E5AE1CE7E8).
+
+## <a id="reference_D5CE64F5FD6F4A808AEFB748C867189E__section_5FF905E0D10D4CDF9E6F49A70848AF69" class="no-quick-link"></a>How can I improve the performance of a partitioned region query?
+
+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?
+
+| Supported elements || |
+|----------|----------|----------|
+| AND | LIMIT | TO_DATE |
+| AS | LIKE | TYPE |
+| COUNT | NOT | WHERE |
+| DISTINCT | NVL | |
+| ELEMENT | OR | |
+| FROM | ORDER BY | |
+| \<HINT\> | SELECT | |
+| IMPORT | SET | |
+| IN | \<TRACE\>| |
+| IS_DEFINED| TRUE | |
+| IS_UNDEFINED | |
+
+For more information and examples on using each supported keyword, see [Supported Keywords](../developing/query_additional/supported_keywords.html#reference_07214B0F8DC94659B0F2D68B67195BD8).
+
+## <a id="reference_D5CE64F5FD6F4A808AEFB748C867189E__section_314B88A55B514B88A12DC36227A2D4EF" class="no-quick-link"></a>How do I debug queries?
+
+You can debug a specific query at the query level by adding the <trace> keyword before the query string that you want to debug. Here is an example:
+
+``` pre
+<trace> SELECT * FROM /exampleRegion
+```
+
+You can also write:
+
+``` pre
+<TRACE> SELECT * FROM /exampleRegion
+```
+
+When the query is executed, Geode 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;
+indexesUsed(0) "select * from /exampleRegion"
+```
+
+If you want to enable debugging for all queries, you can enable query execution logging by setting a System property on the command line during start-up:
+
+``` pre
+gfsh>start server --name=server_name -\u2013J=-Dgemfire.Query.VERBOSE=true
+```
+
+Or you can set the property programmatically:
+
+``` pre
+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:
+
+``` pre
+select distinct value.secId from /pos , getPositions(23)
+```
+
+The following query, however, succeeds because the iterator is either explicitly named with a variable or it is typed:
+
+``` pre
+select distinct e.value.secId from /pos , getPositions(23) e
+
+```
+
+## Can I instruct the query engine to use specific indexes with my queries?
+
+Using HINT *indexname* allows you to instruct the query engine to prefer and filter results from the specified indexes. If you provide multiple index names, the query engine will use all available indexes but prefer the specified indexes.
+
+``` pre
+<HINT 'IDIndex'> SELECT * FROM /Portfolios p WHERE p.ID > 10 AND p.owner = 'XYZ'
+```
+
+``` pre
+<HINT 'IDIndex', 'OwnerIndex'> SELECT * FROM /Portfolios p WHERE p.ID > 10 AND p.owner = 'XYZ' AND p.value < 100
+
+```
+
+## <a id="reference_D5CE64F5FD6F4A808AEFB748C867189E__section_ayq_hqw_1r" class="no-quick-link"></a>How do I perform a case-insensitive search on a field in OQL?
+
+You can use the Java String class methods `toUpperCase` and `toLowerCase` to transform fields where you want to perform a case-insensitive search. For example:
+
+``` pre
+SELECT entry.value FROM /exampleRegion.entries entry WHERE entry.value.toUpperCase LIKE '%BAR%'
+```
+
+or
+
+``` pre
+SELECT * FROM /exampleRegion WHERE foo.toLowerCase LIKE '%bar%'
+```
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/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
new file mode 100644
index 0000000..c994d70
--- /dev/null
+++ b/geode-docs/getting_started/setup_classpath.html.md.erb
@@ -0,0 +1,105 @@
+---
+title: Setting Up the CLASSPATH
+---
+
+This topic describes how Geode 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.
+
+**Note:**
+To embed Geode 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:
+
+<table>
+<colgroup>
+<col width="50%" />
+<col width="50%" />
+</colgroup>
+<thead>
+<tr class="header">
+<th>Geode Process</th>
+<th>Associated JAR Files</th>
+</tr>
+</thead>
+<tbody>
+<tr class="odd">
+<td>gfsh</td>
+<td>gfsh-dependencies.jar</td>
+</tr>
+<tr class="even">
+<td>server and locator</td>
+<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>
+</div></td>
+</tr>
+</tbody>
+</table>
+
+## 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.
+
+**Option 1:** Specify the `--classpath` parameter upon process startup. For example, to modify the CLASSPATH of a locator:
+
+``` pre
+gfsh> start locator --name=locator1 --classpath=/path/to/applications/classes.jar
+```
+
+And to modify the CLASSPATH of a server:
+
+``` pre
+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.
+
+**Option 2:** Define the CLASSPATH environment variable in your OS environment. Then, specify the `--include-system-classpath` parameter upon process startup. For example:
+
+``` pre
+gfsh> start locator --name=locator1 --include-system-classpath=true
+```
+
+The same can also be done for server processes:
+
+``` pre
+gfsh> start server --name=server1 --include-system-classpath=true
+```
+
+This option *appends* the contents of the system CLASSPATH environment variable to the locator or server's CLASSPATH upon startup. Specifying this option without a value sets it to true.
+
+## 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.
+
+For example, to start up a Geode 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"
+org.apache.geode.distributed.LocatorLauncher start locator1
+<locator-launcher-options>
+```
+
+To start up a Geode server process using the ServerLauncher API:
+
+``` pre
+prompt# java -cp "path_to_product/lib/geode-dependencies.jar:/path/to/your/applications/classes.jar"
+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.
+
+To start up an application with an embedded cache:
+
+``` pre
+java -cp "path_to_product/lib/geode-dependencies.jar:/path/to/your/applications/classes.jar"
+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.
+
+
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/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
new file mode 100644
index 0000000..621a3b5
--- /dev/null
+++ b/geode-docs/getting_started/system_requirements/host_machine.html.md.erb
@@ -0,0 +1,32 @@
+---
+title: Host Machine Requirements
+---
+
+Host machines must meet a set of requirements for Apache Geode.
+
+<a id="system_requirements__section_1E1F206FBC8B4A898A449E0699907A7A"></a>
+Each machine that will run Apache Geode 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:
+ - Logs that are useful for troubleshooting. Synchronized time stamps ensure that log messages from different hosts can be merged to reproduce an accurate chronological history of a distributed run.
+ - Aggregate product-level and application-level time statistics.�
+ - Accurate monitoring of the Geode system with scripts and other tools that read the system statistics and log files.
+- The host name and host files are properly configured for the machine. The host name and host file configuration can affect `gfsh` and Pulse functionality.
+- Many default Linux installations use SYN cookies to protect the
+system against malicious attacks that flood TCP SYN packets.
+The use of SYN cookies dramatically reduces network bandwidth,
+and can be triggered by a running GemFire distributed system.
+
+ To disable SYN cookies permanently:
+ 1. Edit the `/etc/sysctl.conf` file to include the following line:
+
+ ``` pre
+ net.ipv4.tcp_syncookies = 0
+ ```
+ Setting this value to zero disables SYN cookies.
+ 2. Reload `sysctl.conf`:
+
+ ``` pre
+ sysctl -p
+ ```
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/getting_started/uninstall_gemfire.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/getting_started/uninstall_gemfire.html.md.erb b/geode-docs/getting_started/uninstall_gemfire.html.md.erb
new file mode 100644
index 0000000..baf19eb
--- /dev/null
+++ b/geode-docs/getting_started/uninstall_gemfire.html.md.erb
@@ -0,0 +1,9 @@
+---
+title: How to Uninstall
+---
+
+This section describes how to remove Geode.
+
+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.
+
+
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/ClientServerAdvancedTopics-5.gif
----------------------------------------------------------------------
diff --git a/geode-docs/images/ClientServerAdvancedTopics-5.gif b/geode-docs/images/ClientServerAdvancedTopics-5.gif
new file mode 100644
index 0000000..4482512
Binary files /dev/null and b/geode-docs/images/ClientServerAdvancedTopics-5.gif differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/ClientServerAdvancedTopics-6.gif
----------------------------------------------------------------------
diff --git a/geode-docs/images/ClientServerAdvancedTopics-6.gif b/geode-docs/images/ClientServerAdvancedTopics-6.gif
new file mode 100644
index 0000000..0191a6c
Binary files /dev/null and b/geode-docs/images/ClientServerAdvancedTopics-6.gif differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/ClientServerAdvancedTopics-7.gif
----------------------------------------------------------------------
diff --git a/geode-docs/images/ClientServerAdvancedTopics-7.gif b/geode-docs/images/ClientServerAdvancedTopics-7.gif
new file mode 100644
index 0000000..0fb0c91
Binary files /dev/null and b/geode-docs/images/ClientServerAdvancedTopics-7.gif differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/ContinuousQuerying-1.gif
----------------------------------------------------------------------
diff --git a/geode-docs/images/ContinuousQuerying-1.gif b/geode-docs/images/ContinuousQuerying-1.gif
new file mode 100644
index 0000000..d989bf1
Binary files /dev/null and b/geode-docs/images/ContinuousQuerying-1.gif differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/ContinuousQuerying-3.gif
----------------------------------------------------------------------
diff --git a/geode-docs/images/ContinuousQuerying-3.gif b/geode-docs/images/ContinuousQuerying-3.gif
new file mode 100644
index 0000000..4bddc6c
Binary files /dev/null and b/geode-docs/images/ContinuousQuerying-3.gif differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/DataManagement-9.png
----------------------------------------------------------------------
diff --git a/geode-docs/images/DataManagement-9.png b/geode-docs/images/DataManagement-9.png
new file mode 100644
index 0000000..9866660
Binary files /dev/null and b/geode-docs/images/DataManagement-9.png differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/DeltaPropagation-1.gif
----------------------------------------------------------------------
diff --git a/geode-docs/images/DeltaPropagation-1.gif b/geode-docs/images/DeltaPropagation-1.gif
new file mode 100644
index 0000000..aa4149e
Binary files /dev/null and b/geode-docs/images/DeltaPropagation-1.gif differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/DeltaPropagation-3.gif
----------------------------------------------------------------------
diff --git a/geode-docs/images/DeltaPropagation-3.gif b/geode-docs/images/DeltaPropagation-3.gif
new file mode 100644
index 0000000..fac17f3
Binary files /dev/null and b/geode-docs/images/DeltaPropagation-3.gif differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/Events-2.gif
----------------------------------------------------------------------
diff --git a/geode-docs/images/Events-2.gif b/geode-docs/images/Events-2.gif
new file mode 100644
index 0000000..6f07fc2
Binary files /dev/null and b/geode-docs/images/Events-2.gif differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/Events-3.gif
----------------------------------------------------------------------
diff --git a/geode-docs/images/Events-3.gif b/geode-docs/images/Events-3.gif
new file mode 100644
index 0000000..3c326ed
Binary files /dev/null and b/geode-docs/images/Events-3.gif differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/FuncExecOnMembers.png
----------------------------------------------------------------------
diff --git a/geode-docs/images/FuncExecOnMembers.png b/geode-docs/images/FuncExecOnMembers.png
new file mode 100644
index 0000000..a00ca1a
Binary files /dev/null and b/geode-docs/images/FuncExecOnMembers.png differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/FuncExecOnRegionHAWithFilter.png
----------------------------------------------------------------------
diff --git a/geode-docs/images/FuncExecOnRegionHAWithFilter.png b/geode-docs/images/FuncExecOnRegionHAWithFilter.png
new file mode 100644
index 0000000..8c0ce15
Binary files /dev/null and b/geode-docs/images/FuncExecOnRegionHAWithFilter.png differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/FuncExecOnRegionNoMetadata.png
----------------------------------------------------------------------
diff --git a/geode-docs/images/FuncExecOnRegionNoMetadata.png b/geode-docs/images/FuncExecOnRegionNoMetadata.png
new file mode 100644
index 0000000..ca0741e
Binary files /dev/null and b/geode-docs/images/FuncExecOnRegionNoMetadata.png differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/FuncExecOnRegionPeersWithFilter.png
----------------------------------------------------------------------
diff --git a/geode-docs/images/FuncExecOnRegionPeersWithFilter.png b/geode-docs/images/FuncExecOnRegionPeersWithFilter.png
new file mode 100644
index 0000000..ad7c3dc
Binary files /dev/null and b/geode-docs/images/FuncExecOnRegionPeersWithFilter.png differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/FuncExecOnRegionWithFilter.png
----------------------------------------------------------------------
diff --git a/geode-docs/images/FuncExecOnRegionWithFilter.png b/geode-docs/images/FuncExecOnRegionWithFilter.png
new file mode 100644
index 0000000..957e00e
Binary files /dev/null and b/geode-docs/images/FuncExecOnRegionWithFilter.png differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/FuncExecOnRegionWithMetadata.png
----------------------------------------------------------------------
diff --git a/geode-docs/images/FuncExecOnRegionWithMetadata.png b/geode-docs/images/FuncExecOnRegionWithMetadata.png
new file mode 100644
index 0000000..66cc824
Binary files /dev/null and b/geode-docs/images/FuncExecOnRegionWithMetadata.png differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/FuncExecOnServers.png
----------------------------------------------------------------------
diff --git a/geode-docs/images/FuncExecOnServers.png b/geode-docs/images/FuncExecOnServers.png
new file mode 100644
index 0000000..44ecae8
Binary files /dev/null and b/geode-docs/images/FuncExecOnServers.png differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/Gemcached.png
----------------------------------------------------------------------
diff --git a/geode-docs/images/Gemcached.png b/geode-docs/images/Gemcached.png
new file mode 100644
index 0000000..1743e66
Binary files /dev/null and b/geode-docs/images/Gemcached.png differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/HibernateFlowchart.png
----------------------------------------------------------------------
diff --git a/geode-docs/images/HibernateFlowchart.png b/geode-docs/images/HibernateFlowchart.png
new file mode 100644
index 0000000..55c500c
Binary files /dev/null and b/geode-docs/images/HibernateFlowchart.png differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/JConsole.png
----------------------------------------------------------------------
diff --git a/geode-docs/images/JConsole.png b/geode-docs/images/JConsole.png
new file mode 100644
index 0000000..cd3e7ab
Binary files /dev/null and b/geode-docs/images/JConsole.png differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/MultiSite-4.gif
----------------------------------------------------------------------
diff --git a/geode-docs/images/MultiSite-4.gif b/geode-docs/images/MultiSite-4.gif
new file mode 100644
index 0000000..c4a4b7d
Binary files /dev/null and b/geode-docs/images/MultiSite-4.gif differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/MultisiteConcurrency_WAN_Gateway.png
----------------------------------------------------------------------
diff --git a/geode-docs/images/MultisiteConcurrency_WAN_Gateway.png b/geode-docs/images/MultisiteConcurrency_WAN_Gateway.png
new file mode 100644
index 0000000..a947b0a
Binary files /dev/null and b/geode-docs/images/MultisiteConcurrency_WAN_Gateway.png differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/SQLite_Persistence_Mgr.png
----------------------------------------------------------------------
diff --git a/geode-docs/images/SQLite_Persistence_Mgr.png b/geode-docs/images/SQLite_Persistence_Mgr.png
new file mode 100644
index 0000000..0384874
Binary files /dev/null and b/geode-docs/images/SQLite_Persistence_Mgr.png differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/Transaction-simple.png
----------------------------------------------------------------------
diff --git a/geode-docs/images/Transaction-simple.png b/geode-docs/images/Transaction-simple.png
new file mode 100644
index 0000000..53965eb
Binary files /dev/null and b/geode-docs/images/Transaction-simple.png differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/consistent_multisite.png
----------------------------------------------------------------------
diff --git a/geode-docs/images/consistent_multisite.png b/geode-docs/images/consistent_multisite.png
new file mode 100644
index 0000000..3ce6f47
Binary files /dev/null and b/geode-docs/images/consistent_multisite.png differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/diskStores-1.gif
----------------------------------------------------------------------
diff --git a/geode-docs/images/diskStores-1.gif b/geode-docs/images/diskStores-1.gif
new file mode 100644
index 0000000..83892b0
Binary files /dev/null and b/geode-docs/images/diskStores-1.gif differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/diskStores-3.gif
----------------------------------------------------------------------
diff --git a/geode-docs/images/diskStores-3.gif b/geode-docs/images/diskStores-3.gif
new file mode 100644
index 0000000..0e725b6
Binary files /dev/null and b/geode-docs/images/diskStores-3.gif differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/jconsole_mbeans.png
----------------------------------------------------------------------
diff --git a/geode-docs/images/jconsole_mbeans.png b/geode-docs/images/jconsole_mbeans.png
new file mode 100644
index 0000000..5c6e6ea
Binary files /dev/null and b/geode-docs/images/jconsole_mbeans.png differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/jvisualvm.png
----------------------------------------------------------------------
diff --git a/geode-docs/images/jvisualvm.png b/geode-docs/images/jvisualvm.png
new file mode 100644
index 0000000..45c095a
Binary files /dev/null and b/geode-docs/images/jvisualvm.png differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/logging-1.gif
----------------------------------------------------------------------
diff --git a/geode-docs/images/logging-1.gif b/geode-docs/images/logging-1.gif
new file mode 100644
index 0000000..021e4f8
Binary files /dev/null and b/geode-docs/images/logging-1.gif differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/member_view_list.png
----------------------------------------------------------------------
diff --git a/geode-docs/images/member_view_list.png b/geode-docs/images/member_view_list.png
new file mode 100644
index 0000000..d25a6a2
Binary files /dev/null and b/geode-docs/images/member_view_list.png differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/multisite-topology-avoid-3.png
----------------------------------------------------------------------
diff --git a/geode-docs/images/multisite-topology-avoid-3.png b/geode-docs/images/multisite-topology-avoid-3.png
new file mode 100644
index 0000000..b1af617
Binary files /dev/null and b/geode-docs/images/multisite-topology-avoid-3.png differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/multisite-topology-hybrid-1.png
----------------------------------------------------------------------
diff --git a/geode-docs/images/multisite-topology-hybrid-1.png b/geode-docs/images/multisite-topology-hybrid-1.png
new file mode 100644
index 0000000..70110fc
Binary files /dev/null and b/geode-docs/images/multisite-topology-hybrid-1.png differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/multisite-topology-hybrid-2.png
----------------------------------------------------------------------
diff --git a/geode-docs/images/multisite-topology-hybrid-2.png b/geode-docs/images/multisite-topology-hybrid-2.png
new file mode 100644
index 0000000..bde8cb3
Binary files /dev/null and b/geode-docs/images/multisite-topology-hybrid-2.png differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/multisite-topology-parallel.png
----------------------------------------------------------------------
diff --git a/geode-docs/images/multisite-topology-parallel.png b/geode-docs/images/multisite-topology-parallel.png
new file mode 100644
index 0000000..75cdff0
Binary files /dev/null and b/geode-docs/images/multisite-topology-parallel.png differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/multisite-topology-serial.png
----------------------------------------------------------------------
diff --git a/geode-docs/images/multisite-topology-serial.png b/geode-docs/images/multisite-topology-serial.png
new file mode 100644
index 0000000..4c0261c
Binary files /dev/null and b/geode-docs/images/multisite-topology-serial.png differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/parallel_sender.png
----------------------------------------------------------------------
diff --git a/geode-docs/images/parallel_sender.png b/geode-docs/images/parallel_sender.png
new file mode 100644
index 0000000..879d8b0
Binary files /dev/null and b/geode-docs/images/parallel_sender.png differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/pulse-data-browser.png
----------------------------------------------------------------------
diff --git a/geode-docs/images/pulse-data-browser.png b/geode-docs/images/pulse-data-browser.png
new file mode 100644
index 0000000..817f05f
Binary files /dev/null and b/geode-docs/images/pulse-data-browser.png differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/pulse-region-detail.png
----------------------------------------------------------------------
diff --git a/geode-docs/images/pulse-region-detail.png b/geode-docs/images/pulse-region-detail.png
new file mode 100644
index 0000000..ea9ba63
Binary files /dev/null and b/geode-docs/images/pulse-region-detail.png differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/pulse_alerts_widget.png
----------------------------------------------------------------------
diff --git a/geode-docs/images/pulse_alerts_widget.png b/geode-docs/images/pulse_alerts_widget.png
new file mode 100644
index 0000000..0228ca7
Binary files /dev/null and b/geode-docs/images/pulse_alerts_widget.png differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/pulse_cluster_view.png
----------------------------------------------------------------------
diff --git a/geode-docs/images/pulse_cluster_view.png b/geode-docs/images/pulse_cluster_view.png
new file mode 100644
index 0000000..ee68756
Binary files /dev/null and b/geode-docs/images/pulse_cluster_view.png differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/pulse_data_view.png
----------------------------------------------------------------------
diff --git a/geode-docs/images/pulse_data_view.png b/geode-docs/images/pulse_data_view.png
new file mode 100644
index 0000000..80b04d6
Binary files /dev/null and b/geode-docs/images/pulse_data_view.png differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/pulse_locator.png
----------------------------------------------------------------------
diff --git a/geode-docs/images/pulse_locator.png b/geode-docs/images/pulse_locator.png
new file mode 100644
index 0000000..37bcf4f
Binary files /dev/null and b/geode-docs/images/pulse_locator.png differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/pulse_member_view.png
----------------------------------------------------------------------
diff --git a/geode-docs/images/pulse_member_view.png b/geode-docs/images/pulse_member_view.png
new file mode 100644
index 0000000..f3520d3
Binary files /dev/null and b/geode-docs/images/pulse_member_view.png differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/rest_example_java_packages.png
----------------------------------------------------------------------
diff --git a/geode-docs/images/rest_example_java_packages.png b/geode-docs/images/rest_example_java_packages.png
new file mode 100644
index 0000000..8fe7a0d
Binary files /dev/null and b/geode-docs/images/rest_example_java_packages.png differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/security-1.gif
----------------------------------------------------------------------
diff --git a/geode-docs/images/security-1.gif b/geode-docs/images/security-1.gif
new file mode 100644
index 0000000..93b337f
Binary files /dev/null and b/geode-docs/images/security-1.gif differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/security-3.gif
----------------------------------------------------------------------
diff --git a/geode-docs/images/security-3.gif b/geode-docs/images/security-3.gif
new file mode 100644
index 0000000..4e6a091
Binary files /dev/null and b/geode-docs/images/security-3.gif differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/security-4.gif
----------------------------------------------------------------------
diff --git a/geode-docs/images/security-4.gif b/geode-docs/images/security-4.gif
new file mode 100644
index 0000000..2a807b0
Binary files /dev/null and b/geode-docs/images/security-4.gif differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/security-5.gif
----------------------------------------------------------------------
diff --git a/geode-docs/images/security-5.gif b/geode-docs/images/security-5.gif
new file mode 100644
index 0000000..7185ec7
Binary files /dev/null and b/geode-docs/images/security-5.gif differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/serial_sender.png
----------------------------------------------------------------------
diff --git a/geode-docs/images/serial_sender.png b/geode-docs/images/serial_sender.png
new file mode 100644
index 0000000..b1cc06a
Binary files /dev/null and b/geode-docs/images/serial_sender.png differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/statistics-1.gif
----------------------------------------------------------------------
diff --git a/geode-docs/images/statistics-1.gif b/geode-docs/images/statistics-1.gif
new file mode 100644
index 0000000..75652f5
Binary files /dev/null and b/geode-docs/images/statistics-1.gif differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/swagger_home.png
----------------------------------------------------------------------
diff --git a/geode-docs/images/swagger_home.png b/geode-docs/images/swagger_home.png
new file mode 100644
index 0000000..c045727
Binary files /dev/null and b/geode-docs/images/swagger_home.png differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/swagger_post_region.png
----------------------------------------------------------------------
diff --git a/geode-docs/images/swagger_post_region.png b/geode-docs/images/swagger_post_region.png
new file mode 100644
index 0000000..b3393c6
Binary files /dev/null and b/geode-docs/images/swagger_post_region.png differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/swagger_post_region_response.png
----------------------------------------------------------------------
diff --git a/geode-docs/images/swagger_post_region_response.png b/geode-docs/images/swagger_post_region_response.png
new file mode 100644
index 0000000..0645dd2
Binary files /dev/null and b/geode-docs/images/swagger_post_region_response.png differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/swagger_v1.png
----------------------------------------------------------------------
diff --git a/geode-docs/images/swagger_v1.png b/geode-docs/images/swagger_v1.png
new file mode 100644
index 0000000..f0dd6b3
Binary files /dev/null and b/geode-docs/images/swagger_v1.png differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/swagger_v1_response.png
----------------------------------------------------------------------
diff --git a/geode-docs/images/swagger_v1_response.png b/geode-docs/images/swagger_v1_response.png
new file mode 100644
index 0000000..c9823df
Binary files /dev/null and b/geode-docs/images/swagger_v1_response.png differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/transactions-client-1.png
----------------------------------------------------------------------
diff --git a/geode-docs/images/transactions-client-1.png b/geode-docs/images/transactions-client-1.png
new file mode 100644
index 0000000..258c4b4
Binary files /dev/null and b/geode-docs/images/transactions-client-1.png differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/transactions_jca_adapter.png
----------------------------------------------------------------------
diff --git a/geode-docs/images/transactions_jca_adapter.png b/geode-docs/images/transactions_jca_adapter.png
new file mode 100644
index 0000000..1f783c7
Binary files /dev/null and b/geode-docs/images/transactions_jca_adapter.png differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/transactions_jta.png
----------------------------------------------------------------------
diff --git a/geode-docs/images/transactions_jta.png b/geode-docs/images/transactions_jta.png
new file mode 100644
index 0000000..f2408f6
Binary files /dev/null and b/geode-docs/images/transactions_jta.png differ
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images/transactions_jta_app_server.png
----------------------------------------------------------------------
diff --git a/geode-docs/images/transactions_jta_app_server.png b/geode-docs/images/transactions_jta_app_server.png
new file mode 100644
index 0000000..7283001
Binary files /dev/null and b/geode-docs/images/transactions_jta_app_server.png differ