geode-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dbar...@apache.org
Subject [02/25] geode-native git commit: Simplify doc directory structure - remove redundant top layer
Date Tue, 14 Feb 2017 20:11:03 GMT
http://git-wip-us.apache.org/repos/asf/geode-native/blob/87b6e035/geode-docs/docs/geode-native-docs/setting-properties/config-overview.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/docs/geode-native-docs/setting-properties/config-overview.html.md.erb b/geode-docs/docs/geode-native-docs/setting-properties/config-overview.html.md.erb
deleted file mode 100644
index c84535d..0000000
--- a/geode-docs/docs/geode-native-docs/setting-properties/config-overview.html.md.erb
+++ /dev/null
@@ -1,31 +0,0 @@
----
-title:  Configuring the Native Client and Cache Server
----
-
-You can configure clients through files and API calls. The servers are configured through command-line input and configuration files.
-
--   **[Native Client Configuration](native-client-config.html)**
-
-    You configure the native client in two files: `gfcpp.properties` for native client system-level configuration and `cache.xml` for cache-level configuration.
-
--   **[Cache Server Configuration](cache-server-config.html)**
-
-    You configure the cache server in two files: `gemfire.properties` for server system-level configuration and `cache.xml` for cache-level configuration.
-
--   **[Attribute Definition Priority](attribute-def-priority.html)**
-
-    You can specify attributes in different ways, which can cause conflicting definitions. Applications can be configured programmatically, and that has priority over other settings.
-
--   **[Search Path for Multiple gfcpp.properties Files](../gfcpp.properties/gfcpp.properties_search_path.html)**
-
-    The native client and cache server processes first look for their properties file in the <code>_product-dir_/defaultSystem</code> directory, then in the working directory.
-
--   **[Overriding gfcpp.properties Settings](../gfcpp.properties/overriding_gfcpp.properties.html)**
-
-    Application developers have the option of configuring system attributes programmatically, rather than using the `gfcpp.properties` file.
-
--   **[Defining Properties Programmatically](define-programmatically.html)**
-
-    You can pass in specific gfcpp properties programmatically by using a `Properties` object to define the non-default properties.
-
-

http://git-wip-us.apache.org/repos/asf/geode-native/blob/87b6e035/geode-docs/docs/geode-native-docs/setting-properties/define-programmatically.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/docs/geode-native-docs/setting-properties/define-programmatically.html.md.erb b/geode-docs/docs/geode-native-docs/setting-properties/define-programmatically.html.md.erb
deleted file mode 100644
index 94141d6..0000000
--- a/geode-docs/docs/geode-native-docs/setting-properties/define-programmatically.html.md.erb
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title:  Defining Properties Programmatically
----
-
-You can pass in specific gfcpp properties programmatically by using a `Properties` object to define the non-default properties.
-
-Example:
-
-``` pre
-PropertiesPtr systemProps = Properties::create();
-systemProps->insert( "statistic-archive-file", "stats.gfs" );
-systemProps->insert( "cache-xml-file", "./myapp-cache.xml" );
-systemProps->insert( "stacktrace-enabled", "true" );
-CacheFactoryPtr systemPtr = CacheFactory::createCacheFactory(systemProps);
-    
-```
-
-

http://git-wip-us.apache.org/repos/asf/geode-native/blob/87b6e035/geode-docs/docs/geode-native-docs/setting-properties/native-client-config.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/docs/geode-native-docs/setting-properties/native-client-config.html.md.erb b/geode-docs/docs/geode-native-docs/setting-properties/native-client-config.html.md.erb
deleted file mode 100644
index 69216ae..0000000
--- a/geode-docs/docs/geode-native-docs/setting-properties/native-client-config.html.md.erb
+++ /dev/null
@@ -1,35 +0,0 @@
----
-title:  Native Client Configuration
----
-
-You configure the native client in two files: `gfcpp.properties` for native client system-level configuration and `cache.xml` for cache-level configuration.
-
-The configuration of the caches is part of the application development process. See [Cache Initialization File](../cache-init-file/chapter-overview.html#chapter-overview). (The cache-level configuration file is generally referred to as `cache.xml`, but you can use any name.)
-
-## <a id="native-client-config__section_67D24B8F8C6C46CDA3474E6E42963D04" class="no-quick-link"></a>About gfcpp.properties Configuration File
-
-The `gfcpp.properties` file provides local settings required to connect a client to a distributed system, along with settings for licensing, logging, and statistics. See [Attributes in gfcpp.properties](attributes-gfcpp.html#attributes-gfcpp).
-
-The application software may include a set of `gfcpp.properties` files. You set any attributes needed for the application design in these files, then you can add any attributes needed for the local site.
-
-If you do not have `gfcpp.properties` files, use any text editor to create them. See [gfcpp.properties Example File](../gfcpp.properties/chapter_overview.html#concept_41DADD6F4E41495A89CCBB8A790ED9DF) for a sample of the file format and contents.
-
-## <a id="native-client-config__section_88780874FD6C4BBD9B1B993758A985BB" class="no-quick-link"></a>Configuration File Locations
-
-A native client looks for `gfcpp.properties` first in the working directory where the process runs, then in <code>_product-dir_/defaultSystem</code>.
-Use the `defaultSystem` directory to group configuration files or to share them among processes for more convenient administration. If `gfcpp.properties` is not found, the process starts up with the default settings.
-
-For the `cache.xml` cache configuration file, a native client looks for the path specified by the `cache-xml-file` attribute in `gfcpp.properties` (see [Attributes in gfcpp.properties](attributes-gfcpp.html#attributes-gfcpp)). If the `cache.xml` is not found, the process starts with an unconfigured cache.
-
-## <a id="native-client-config__section_6EBE269F15A1497BB4ABBF659F978DA1" class="no-quick-link"></a>Configuring System Properties for the Native Client
-
-The typical configuration procedure for a native client includes the high-level steps listed below. The rest of this chapter provides the details.
-
-1.  Place the `gfcpp.properties` file for the application in the working directory or in <code>_product-dir_/defaultSystem</code>.
-Use the configuration file that came with the application software if there is one, or create your own. See [gfcpp.properties Example File](../gfcpp.properties/chapter_overview.html#concept_41DADD6F4E41495A89CCBB8A790ED9DF) for a sample of the file format and contents.
-2.  Place the `cache.xml` file for the application in the desired location and specify its path in the `gfcpp.properties` file.
-3.  Add other attributes to the `gfcpp.properties` file as needed for the local system architecture. See [Attributes in gfcpp.properties](attributes-gfcpp.html#attributes-gfcpp) for the configurable attributes, and [gfcpp.properties Example File](../gfcpp.properties/chapter_overview.html#concept_41DADD6F4E41495A89CCBB8A790ED9DF) for a sample of the file format.
-
-## <a id="native-client-config__section_7F09E85DD0144972AAA7028D81780129" class="no-quick-link"></a>Running a Native Client Out of the Box
-
-If you start a native client without any configurations, it uses any attributes set programmatically plus any hard-coded defaults (listed in [Attributes in gfcpp.properties](attributes-gfcpp.html#attributes-gfcpp)). Running with the defaults is a convenient way to learn the operation of the distributed system and to test which attributes need to be reconfigured for your environment.

http://git-wip-us.apache.org/repos/asf/geode-native/blob/87b6e035/geode-docs/docs/geode-native-docs/sqlite-persistence/chapter_overview.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/docs/geode-native-docs/sqlite-persistence/chapter_overview.html.md.erb b/geode-docs/docs/geode-native-docs/sqlite-persistence/chapter_overview.html.md.erb
deleted file mode 100644
index 7c95e7d..0000000
--- a/geode-docs/docs/geode-native-docs/sqlite-persistence/chapter_overview.html.md.erb
+++ /dev/null
@@ -1,21 +0,0 @@
----
-title:  Installing the SQLite Persistence Manager
----
-
-This section describes how to download, build and install the SQLite database libraries for use with disk overflow.
-
-See [PersistenceManager](../client-cache/persistence-manager.html#persistence-manager) for additional information about the SQLite database libraries.
-
--   **[Linux Installation](linux_install.html)**
-
-    This topic describes how to install the SQLite Persistence Manager on Linux for use with the Geode native client.
-
--   **[Solaris Installation](solaris_install.html)**
-
-    This topic describes how to install the SQLite Persistence Manager on Solaris for use with the Geode native client.
-
--   **[Windows Installation](windows_install.html)**
-
-    This topic describes how to install the SQLite Persistence Manager on Windows for use with the Geode native client.
-
-

http://git-wip-us.apache.org/repos/asf/geode-native/blob/87b6e035/geode-docs/docs/geode-native-docs/sqlite-persistence/linux_install.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/docs/geode-native-docs/sqlite-persistence/linux_install.html.md.erb b/geode-docs/docs/geode-native-docs/sqlite-persistence/linux_install.html.md.erb
deleted file mode 100644
index 3bbdb2c..0000000
--- a/geode-docs/docs/geode-native-docs/sqlite-persistence/linux_install.html.md.erb
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title:  Linux Installation
----
-
-This topic describes how to install the SQLite Persistence Manager on Linux for use with the Geode native client.
-
-The <code>_product-dir_</code> directory refers to the path to the native client product directory.
-
-The following libraries must be present in the runtime linking path:
-
--   `libSqLiteImpl.so` is provided in <code>_product-dir_/lib</code>, so it is already present in the runtime linking path.
--   `libsqlite3.so` is the SQLite Library. You need to create this library and make available in the runtime linking path, or copied to <code>_product-dir_/lib</code>, as described below.
-
-The Geode Native Client has been tested with SQLite v3.7.14.1.
-
-## <a id="concept_CC9BD47B46DE4281BBB789FABE6ABEA9__section_FAB703D706D54311963399A714D466F9" class="no-quick-link"></a>Downloading, Building and Installing the Library
-
-You create the SQLite database library by downloading the latest .zip file and compiling the source code.
-
-1.  Download the source code `sqlite-autoconf-NNNNNNN.tar.gz` file (where *NNNNNNN* corresponds to the version) for SQLite v3.7.14.1 or later from [http://www.sqlite.org/download.html](http://www.sqlite.org/download.html).
-2.  Extract the source code from the .tar.gz file. For example:
-
-    ``` pre
-    tar -xvf sqlite-autoconf-3071401.tar.gz
-    ```
-
-3.  Change directories to the extracted source files, and follow the install instructions located in the "INSTALL" file.
-    1.  Run the `configure` command for 32-bit or 64-bit with the following options, all entered on a single command line. Change the` --prefix` directory specification to the location where you want the libraries:
-        -   **32-bit:**
-
-            <code>
-            CFLAGS="-m32" ./configure --prefix=/_desired-binary-location_/sqlite-binaries
-            </code>
-        -   **64-bit:**
-
-            <code>
-            ./configure --prefix=/_desired-binary-location_/sqlite-binaries
-            </code>
-
-    2.  Run `gmake install` as described in the build instructions. The libraries will be available in the `sqlite-binaries` directory that you specified.
-
-4.  Copy <code>/_desired-binary-location_/sqlite-binaries/lib/libsqlite3.so</code> file to <code>_product-dir_/lib</code>.

http://git-wip-us.apache.org/repos/asf/geode-native/blob/87b6e035/geode-docs/docs/geode-native-docs/sqlite-persistence/solaris_install.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/docs/geode-native-docs/sqlite-persistence/solaris_install.html.md.erb b/geode-docs/docs/geode-native-docs/sqlite-persistence/solaris_install.html.md.erb
deleted file mode 100644
index 6ecd67f..0000000
--- a/geode-docs/docs/geode-native-docs/sqlite-persistence/solaris_install.html.md.erb
+++ /dev/null
@@ -1,54 +0,0 @@
----
-title:  Solaris Installation
----
-
-This topic describes how to install the SQLite Persistence Manager on Solaris for use with the Geode native client.
-
-The *`product-dir`* directory refers to the path to the native client product directory.
-
-The following libraries must be present in the runtime linking path:
-
--   `libSqLiteImpl.so` is provided in <code><i>product-dir</i>/lib</code>, so it is already present in the runtime linking path.
--   `libsqlite3.so` is the SQLite Library. You need to create this library and make available in the runtime linking path, or copied to <code><i>product-dir</i>/lib</code>, as described below.
-
-The Geode Native Client has been tested with SQLite v3.7.14.1.
-
-## <a id="concept_613BCAD15D9C4B3C94BBA3C1A26B6166__section_FAB703D706D54311963399A714D466F9" class="no-quick-link"></a>Downloading, Building, and Installing the Library
-
-You create the SQLite database library by downloading the latest .zip file and compiling the source code.
-
-1.  Download the source code `sqlite-autoconf-NNNNNNN.tar.gz` file (where *NNNNNNN* corresponds to the version) for SQLite v3.7.14.1 or later from [http://www.sqlite.org/download.html](http://www.sqlite.org/download.html).
-2.  Update your PATH environment variable to include the location of the Solaris `ar` command.
-
-    ``` pre
-    export PATH=/usr/css/bin:$PATH
-    ```
-
-3.  Extract the source code from the .tar.gz file. First unzip:
-
-    ``` pre
-    gzip -d sqlite-autoconf-3071401.tar.gz
-    ```
-
-    Then untar the file:
-
-    ``` pre
-    tar -xvf sqlite-autoconf-3071401.tar
-    ```
-
-4.  Change directories to the extracted source files, and follow the install instructions located in the "INSTALL" file.
-    1.  Run the `configure` command for 32-bit or 64-bit Solaris systems with the following options, all entered on a single command line. Change the` --prefix` directory specification to the location where you want the libraries:
-        -   **32-bit:**
-
-            <code>
-            CC=cc CFLAGS="-xarch=v8plus -code=pic32" ./configure --prefix=/_desired-binary-location_/sqlite-binaries
-            </code>
-        -   **64-bit:**
-
-            <code>
-            CC=cc CFLAGS="-xarch=v9 -code=pic32" ./configure --prefix=/_desired-binary-location_/sqlite-binaries CFLAGS="-m64"
-            </code>
-
-    2.  Run `gmake install`. The libraries will be available in the `sqlite-binaries` directory that you specified.
-
-5.  Copy <code>/_desired-binary-location_/sqlite-binaries/lib/libsqlite3.so</code> file to <code><i>product-dir</i>/lib</code>.

http://git-wip-us.apache.org/repos/asf/geode-native/blob/87b6e035/geode-docs/docs/geode-native-docs/sqlite-persistence/windows_install.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/docs/geode-native-docs/sqlite-persistence/windows_install.html.md.erb b/geode-docs/docs/geode-native-docs/sqlite-persistence/windows_install.html.md.erb
deleted file mode 100644
index 8c8cbc4..0000000
--- a/geode-docs/docs/geode-native-docs/sqlite-persistence/windows_install.html.md.erb
+++ /dev/null
@@ -1,37 +0,0 @@
----
-title:  Windows Installation
----
-
-This topic describes how to install the SQLite Persistence Manager on Windows for use with the Geode native client.
-
-The Geode Native Client has been tested with SQLite v3.7.14.1.
-
-The <code><i>product-dir</i></code> directory refers to the native client product directory path.
-
-The following libraries are required. The <code><i>product-dir</i>/bin</code> directory containing these libraries must be present in the Windows `PATH` environment variable, and that directory is added to `PATH` during the Geode product installation.
-
--   The `sqliteimpl.dll` and `GemStone.GemFire.Plugins.SQLite.dll` files are provided in <code><i>product-dir</i>/bin</code>.
--   For .NET C\# native client application development, you need to obtain the `System.Data.SQLite.dll` SQLite library, as described below. The library can be copied to <code><i>product-dir</i>/bin</code>.
--   For C++ native client application development, you need the `SqLite3.dll` SQLite Library. You create this library and make it available in the runtime linking path, or copied to <code><i>product-dir</i>/bin</code>, as described below.
-
-## <a id="concept_E097592856274EFABE81426FF7312294__section_270FDD34D5D1460DAF0FD2DD4E8FB31A" class="no-quick-link"></a>Downloading Pre-built System.Data.SQLite.dll Binaries
-
-If you are writing native client applications using the .NET caching API, obtain the SQLite library (version 3.12.2 or later) for Windows as follows:
-
-1.  Access the System.Data.SQLite Download Page at the following URL: [http://system.data.sqlite.org/index.html/doc/trunk/www/downloads.wiki](http://system.data.sqlite.org/index.html/doc/trunk/www/downloads.wiki).
-2.  Download the appropriate setup file for your .NET Framework installation and hardware architecture.
-    -   For 64-bit Windows, under **Precompiled Binaries for 64-bit Windows (.NET Framework 4.5.1)** download `sqlite-netFx451-binary-bundle-x64-2013-1.0.101.0.zip`.
-
-3.  Execute the setup .exe file, and follow the prompts in the installation wizard. Accept all default installation options.
-4.  Copy the `C:\Program                         Files\System.Data.SQLite\2010\bin\System.Data.SQLite.dll` file to your Geode Native Client distribution at <code>_product-dir_\bin</code>.
-
-## <a id="concept_E097592856274EFABE81426FF7312294__section_FAB703D706D54311963399A714D466F9" class="no-quick-link"></a>Downloading, Building, and Installing the Library
-
-If you are writing native client applications using the C++ caching API, you need to build the SQLite solution for your Windows platform architecture.
-
-1.  Download the source code `sqlite-autoconf-NNNNNNN.tar.gz` file (where *NNNNNNN* corresponds to the version) for SQLite version 3.12.2 or later from [http://www.sqlite.org/download.html](http://www.sqlite.org/download.html).
-2.  Extract the source code from the .tar.gz file. You may need to use CygWin or a Windows-compatible tar extraction tool.
-3.  Using Visual Studio, build the version-specific SqLite solution either as a release or debug build:
-    -   If you are using 64-bit Windows, use the x64 configuration.
-
-4.  From the built files, copy the `SqLite3.dll` file to your Geode Native Client distribution at <code><i>product-dir</i>/bin</code>.

http://git-wip-us.apache.org/repos/asf/geode-native/blob/87b6e035/geode-docs/docs/geode-native-docs/system-statistics/cache_performance_statistics.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/docs/geode-native-docs/system-statistics/cache_performance_statistics.html.md.erb b/geode-docs/docs/geode-native-docs/system-statistics/cache_performance_statistics.html.md.erb
deleted file mode 100644
index 0edcb18..0000000
--- a/geode-docs/docs/geode-native-docs/system-statistics/cache_performance_statistics.html.md.erb
+++ /dev/null
@@ -1,30 +0,0 @@
----
-title:  Cache Performance Statistics
----
-
-Use cache performance statistics to determine the type and number of cache operations being performed and how much time they consume.
-
-These statistics are available if the member creates a cache.
-
-|                                  |                                                                                              |
-|----------------------------------|----------------------------------------------------------------------------------------------|
-| `creates`                        | Total number of cache creates.                                                               |
-| `puts`                           | Total number of cache puts.                                                                  |
-| `gets`                           | Total number of cache gets.                                                                  |
-| `entries`                        | Current number of cache entries.                                                             |
-| `hits`                           | Total number of cache hits.                                                                  |
-| `misses`                         | Total number of cache misses.                                                                |
-| `destroys`                       | Total number of cache destroys.                                                              |
-| `overflows`                      | Total number of cache overflows to persistence backup.                                       |
-| `cacheListenerCallsCompleted`    | Total number of times a cache listener call has completed.                                   |
-| `pdxInstanceDeserializations`    | Total number of times getObject has been called on a PdxInstance.                            |
-| `pdxInstanceDeserializationTime` | Total amount of time, in nanoseconds, spent deserializing PdxInstances by calling getObject. |
-| `pdxInstanceCreations`           | Total number of times a deserialization created a PdxInstance.                               |
-| `pdxSerializations`              | Total number of PDX serializations.                                                          |
-| `pdxSerializedBytes`             | Total number of bytes produced by PDX serialization.                                         |
-| `pdxDeserializations`            | Total number of PDX deserializations.                                                        |
-| `pdxDeserializedBytes`           | Total number of bytes read by PDX deserialization.                                           |
-| `tombstoneCount`                 | Total number of tombstone entries created for performing concurrency checks.                 |
-| `nonReplicatedTombstoneSize`     | Approximate total size (in bytes) of tombstones present in the client cache.                 |
-
-

http://git-wip-us.apache.org/repos/asf/geode-native/blob/87b6e035/geode-docs/docs/geode-native-docs/system-statistics/chapter_overview.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/docs/geode-native-docs/system-statistics/chapter_overview.html.md.erb b/geode-docs/docs/geode-native-docs/system-statistics/chapter_overview.html.md.erb
deleted file mode 100644
index 38c69b8..0000000
--- a/geode-docs/docs/geode-native-docs/system-statistics/chapter_overview.html.md.erb
+++ /dev/null
@@ -1,21 +0,0 @@
----
-title:  System Statistics
----
-
-*System Statistics* provides information on the Pivotal GemFire installation and includes standard statistics for caching and distribution activities.
-
-Statistics that end with "time" are time-based statistics. For performance reasons, by default, the system does not collect these. To enable time-based statistics gathering, set the system property` enable-time-statistics` in [Attributes in gfcpp.properties—Statistics Archiving Properties](../setting-properties/attributes-gfcpp.html#attributes-gfcpp__table_E1A0EDBA67CD41319E1E5FD0A0BB2723).
-
--   **[Sampling Statistics](sampling_statistics.html)**
-
-    When applications and cache servers join a distributed system, they indicate whether to enable statistics sampling and whether to archive the statistics that are gathered.
-
--   **[System Performance Statistics](system_performance_statistics.html)**
-
-    Performance statistics are collected for each application or cache server that connects to a distributed system.
-
--   **[Operating System Statistics](operating_system_statistics.html)**
-
-    Use operating system statistics to determine a member’s CPU, memory, and disk usage.
-
-

http://git-wip-us.apache.org/repos/asf/geode-native/blob/87b6e035/geode-docs/docs/geode-native-docs/system-statistics/continuous_query_statistics.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/docs/geode-native-docs/system-statistics/continuous_query_statistics.html.md.erb b/geode-docs/docs/geode-native-docs/system-statistics/continuous_query_statistics.html.md.erb
deleted file mode 100644
index 7e463e0..0000000
--- a/geode-docs/docs/geode-native-docs/system-statistics/continuous_query_statistics.html.md.erb
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title:  Continuous Query Statistics
----
-
-Continuous query statistics give you information about a registered Continuous Query (CQ) represented by the CqQuery object.
-
-|            |                                            |
-|------------|--------------------------------------------|
-| `inserts`  | Total number of inserts for this CQ query. |
-| `updates ` | Total number of updates for this CQ query. |
-| `deletes`  | Total number of deletes for this CQ query. |
-| `events`   | Total number of events for this CQ query.  |
-
-

http://git-wip-us.apache.org/repos/asf/geode-native/blob/87b6e035/geode-docs/docs/geode-native-docs/system-statistics/cq_service_statistics.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/docs/geode-native-docs/system-statistics/cq_service_statistics.html.md.erb b/geode-docs/docs/geode-native-docs/system-statistics/cq_service_statistics.html.md.erb
deleted file mode 100644
index 24db7b1..0000000
--- a/geode-docs/docs/geode-native-docs/system-statistics/cq_service_statistics.html.md.erb
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title:  CQ Service Statistics
----
-
-Use CQ service methods to get aggregate statistical information about the continuous queries of a client.
-
-|                |                                                        |
-|----------------|--------------------------------------------------------|
-| `CqsActive`    | Total number of CQs active for this CQ service.        |
-| `CqsCreated `  | Total number of CQs created for this CQ service.       |
-| `CqsClosed `   | Total number of CQs closed for this CQ service.        |
-| `CqsStopped`   | Total number of CQs stopped for this CQ service.       |
-| `CqsOnClient ` | Total number of CQs on the client for this CQ service. |
-
-

http://git-wip-us.apache.org/repos/asf/geode-native/blob/87b6e035/geode-docs/docs/geode-native-docs/system-statistics/delta_statistics.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/docs/geode-native-docs/system-statistics/delta_statistics.html.md.erb b/geode-docs/docs/geode-native-docs/system-statistics/delta_statistics.html.md.erb
deleted file mode 100644
index b9b6b32..0000000
--- a/geode-docs/docs/geode-native-docs/system-statistics/delta_statistics.html.md.erb
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title:  Delta Statistics
----
-
-Delta statistics provide information about updates to data.
-
-|                              |                                                                                                              |
-|------------------------------|--------------------------------------------------------------------------------------------------------------|
-| `deltaMessageFailures`       | Total number of messages containing delta (received from server) but could not be processed after reception. |
-| `deltaPuts`                  | Total number of puts containing delta that have been sent from client to server.                             |
-| `processedDeltaMessages`     | Total number of messages containing delta received from server and processed after reception.                |
-| `processedDeltaMessagesTime` | Total time spent applying delta (received from server) on existing values at client.                         |
-
-

http://git-wip-us.apache.org/repos/asf/geode-native/blob/87b6e035/geode-docs/docs/geode-native-docs/system-statistics/linux_os_statistics.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/docs/geode-native-docs/system-statistics/linux_os_statistics.html.md.erb b/geode-docs/docs/geode-native-docs/system-statistics/linux_os_statistics.html.md.erb
deleted file mode 100644
index ab4d2b3..0000000
--- a/geode-docs/docs/geode-native-docs/system-statistics/linux_os_statistics.html.md.erb
+++ /dev/null
@@ -1,17 +0,0 @@
----
-title:  Linux Process Statistics
----
-
-Use these methods to get information about a Linux operating system process that is using a Geode system.
-
-|                     |                                                                          |
-|---------------------|--------------------------------------------------------------------------|
-| `imageSize`         | The size of the process's image in megabytes.                            |
-| `rssSize`           | The size of the process's resident set size in megabytes.                |
-| `userTime`          | The operating system statistic for the process CPU usage in user time    |
-| `systemTime`        | The operating system statistic for the process CPU usage in system time. |
-| `hostCpuUsage`      | The operating system statistic for the host CPU usage.                   |
-| `threads`           | Number of threads currently active in this process.                      |
-| `LinuxProcessStats` | Statistics for a Linux process.                                          |
-
-

http://git-wip-us.apache.org/repos/asf/geode-native/blob/87b6e035/geode-docs/docs/geode-native-docs/system-statistics/operating_system_statistics.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/docs/geode-native-docs/system-statistics/operating_system_statistics.html.md.erb b/geode-docs/docs/geode-native-docs/system-statistics/operating_system_statistics.html.md.erb
deleted file mode 100644
index f6c955e..0000000
--- a/geode-docs/docs/geode-native-docs/system-statistics/operating_system_statistics.html.md.erb
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title:  Operating System Statistics
----
-
-Use operating system statistics to determine a member’s CPU, memory, and disk usage.
-
--   **[Linux Process Statistics](linux_os_statistics.html)**
-
-    Use these methods to get information about a Linux operating system process that is using a GemFire system.
-
--   **[Solaris Process Statistics](solaris_os_statistics.html)**
-
-    Use these methods to get information about a Solaris operating system process that is using a GemFire system
-
--   **[Windows Process Statistics](windows_os_statistics.html)**
-
-    Use these methods to get information about a Windows operating system process that is using a GemFire system.
-
-

http://git-wip-us.apache.org/repos/asf/geode-native/blob/87b6e035/geode-docs/docs/geode-native-docs/system-statistics/pool_statistics.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/docs/geode-native-docs/system-statistics/pool_statistics.html.md.erb b/geode-docs/docs/geode-native-docs/system-statistics/pool_statistics.html.md.erb
deleted file mode 100644
index cc51aa4..0000000
--- a/geode-docs/docs/geode-native-docs/system-statistics/pool_statistics.html.md.erb
+++ /dev/null
@@ -1,30 +0,0 @@
----
-title:  Pool Statistics
----
-
-Use the pool object to get statistics on connection pools.
-
-|                               |                                                                                                               |
-|-------------------------------|---------------------------------------------------------------------------------------------------------------|
-| `locators`                    | Current number of locators discovered.                                                                        |
-| `servers`                     | Current number of servers discovered.                                                                         |
-| `locatorRequests`             | Number of requests from this connection pool to a locator.                                                    |
-| `locatorResponses`            | Number of responses from the locator to this connection pool.                                                 |
-| `poolConnections`             | Current number of pool connections.                                                                           |
-| `connects`                    | Total number of times a connection has been created.                                                          |
-| `ConnectionWaitTime`          | Total time (nanoseconds) spent waiting for a connection.                                                      |
-| `disconnects`                 | Total number of times a connection has been destroyed.                                                        |
-| `minPoolSizeConnect`          | Total number of connects done to maintain minimum pool size.                                                  |
-| `loadConditioningConnects`    | Total number of connects done due to load conditioning.                                                       |
-| `idleDisconnects`             | Total number of disconnects done due to idle expiration.                                                      |
-| `loadConditioningDisconnects` | Total number of disconnects done due to load conditioning expiration.                                         |
-| `connectionWaitsInProgress`   | Current number of threads waiting for a connection.                                                           |
-| `connectionWaits`             | Total number of times a thread completed waiting for a connection (by timing out or by getting a connection). |
-| `clientOpsInProgress`         | Current number of clientOps being executed.                                                                   |
-| `clientOps`                   | Total number of clientOps completed successfully.                                                             |
-| `clientOpFailures`            | Total number of clientOp attempts that have failed.                                                           |
-| `clientOpTimeouts`            | Total number of clientOp attempts that have timed out.                                                        |
-| `QueryExecutions`             | Total number of queryExecutions.                                                                              |
-| `QueryExecutionTime`          | Total time spent while processing queryExecution.                                                             |
-
-

http://git-wip-us.apache.org/repos/asf/geode-native/blob/87b6e035/geode-docs/docs/geode-native-docs/system-statistics/region_statistics.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/docs/geode-native-docs/system-statistics/region_statistics.html.md.erb b/geode-docs/docs/geode-native-docs/system-statistics/region_statistics.html.md.erb
deleted file mode 100644
index 4df1fae..0000000
--- a/geode-docs/docs/geode-native-docs/system-statistics/region_statistics.html.md.erb
+++ /dev/null
@@ -1,113 +0,0 @@
----
-title:  Region Statistics
----
-
-These methods help you to get the statistics of a region.
-
-<a id="concept_7AA863080074439286F4F51048BC2159__section_8A343C8D6425469DA314D9A96E543A24"></a>
-<table>
-<colgroup>
-<col width="50%" />
-<col width="50%" />
-</colgroup>
-<tbody>
-<tr class="odd">
-<td><code class="ph codeph">creates</code></td>
-<td>Total number of cache creates for this region.</td>
-</tr>
-<tr class="even">
-<td><code class="ph codeph">puts</code></td>
-<td>Total number of cache put operations for this region.</td>
-</tr>
-<tr class="odd">
-<td><code class="ph codeph">putTime</code></td>
-<td>Total time spent doing put operations for this region.</td>
-</tr>
-<tr class="even">
-<td><code class="ph codeph">putAll</code></td>
-<td>Total number of cache putAlls for this region.</td>
-</tr>
-<tr class="odd">
-<td><code class="ph codeph">putAllTime</code></td>
-<td>Total time spent doing putAll operations for this region.</td>
-</tr>
-<tr class="even">
-<td><code class="ph codeph">gets</code></td>
-<td>Total number of cache gets for this region.</td>
-</tr>
-<tr class="odd">
-<td><code class="ph codeph">getTime</code></td>
-<td><p>Total time spent doing get operations for this region.</p></td>
-</tr>
-<tr class="even">
-<td><code class="ph codeph">getAll</code></td>
-<td>Total number of cache getAlls for this region.</td>
-</tr>
-<tr class="odd">
-<td><code class="ph codeph">getAllTime</code></td>
-<td>Total time spent doing getAll operations for this region.</td>
-</tr>
-<tr class="even">
-<td><code class="ph codeph">hits</code></td>
-<td>Total number of cache hits for this region.</td>
-</tr>
-<tr class="odd">
-<td><code class="ph codeph">misses</code></td>
-<td>Total number of cache misses for this region.</td>
-</tr>
-<tr class="even">
-<td><code class="ph codeph">entries</code></td>
-<td>Current number of cache entries for this region.</td>
-</tr>
-<tr class="odd">
-<td><code class="ph codeph">destroys</code></td>
-<td>Total number of cache destroys for this region.</td>
-</tr>
-<tr class="even">
-<td><code class="ph codeph">clears</code></td>
-<td>Total number of cache clears for this region.</td>
-</tr>
-<tr class="odd">
-<td><code class="ph codeph">overflows</code></td>
-<td>Total number of cache overflows to disk for this region.</td>
-</tr>
-<tr class="even">
-<td><code class="ph codeph">retrieves</code></td>
-<td>Total number of cache entries fetched from disk into the cache region.</td>
-</tr>
-<tr class="odd">
-<td><code class="ph codeph">nonSingleHopCount</code></td>
-<td>Total number of times client request required multiple hops.</td>
-</tr>
-<tr class="even">
-<td><code class="ph codeph">metaDataRefreshCount</code></td>
-<td>Total number of times metadata was refreshed due to the observation of multiple hops.</td>
-</tr>
-<tr class="odd">
-<td><code class="ph codeph">cacheLoaderCallCompleted</code></td>
-<td>Total number of times a load has completed for this region.</td>
-</tr>
-<tr class="even">
-<td><code class="ph codeph">cacheLoaderCallTime</code></td>
-<td>Total time spent invoking the loaders for this region.</td>
-</tr>
-<tr class="odd">
-<td><code class="ph codeph">CacheWriterCallsCompleted</code></td>
-<td>Total number of times a cache writer call has completed for this region.</td>
-</tr>
-<tr class="even">
-<td><code class="ph codeph">CacheWriterCallTime</code></td>
-<td>Total time spent doing cache writer calls.</td>
-</tr>
-<tr class="odd">
-<td><code class="ph codeph">CacheListenerCallsCompleted</code></td>
-<td>Total number of times a cache listener call has completed for this region.</td>
-</tr>
-<tr class="even">
-<td><code class="ph codeph">CacheListenerCallTime</code></td>
-<td>Total time spent doing cache listener calls for this region.</td>
-</tr>
-</tbody>
-</table>
-
-

http://git-wip-us.apache.org/repos/asf/geode-native/blob/87b6e035/geode-docs/docs/geode-native-docs/system-statistics/sampling_statistics.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/docs/geode-native-docs/system-statistics/sampling_statistics.html.md.erb b/geode-docs/docs/geode-native-docs/system-statistics/sampling_statistics.html.md.erb
deleted file mode 100644
index f8f4b68..0000000
--- a/geode-docs/docs/geode-native-docs/system-statistics/sampling_statistics.html.md.erb
+++ /dev/null
@@ -1,17 +0,0 @@
----
-title:  Sampling Statistics
----
-
-When applications and cache servers join a distributed system, they indicate whether to enable statistics sampling and whether to archive the statistics that are gathered.
-
-The following statistics are related to the statistic sampler.
-
-|               |                                                |
-|---------------|------------------------------------------------|
-| `sampleCount` | Total number of samples taken by this sampler. |
-| `sampleTime`  | Total amount of time spent taking samples.     |
-| `StatSampler` | Statistics on the statistic sampler.           |
-
-For more information about configuring statistics, see [Attributes in gfcpp.properties](../setting-properties/attributes-gfcpp.html#attributes-gfcpp).
-
-

http://git-wip-us.apache.org/repos/asf/geode-native/blob/87b6e035/geode-docs/docs/geode-native-docs/system-statistics/solaris_os_statistics.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/docs/geode-native-docs/system-statistics/solaris_os_statistics.html.md.erb b/geode-docs/docs/geode-native-docs/system-statistics/solaris_os_statistics.html.md.erb
deleted file mode 100644
index 4b19b37..0000000
--- a/geode-docs/docs/geode-native-docs/system-statistics/solaris_os_statistics.html.md.erb
+++ /dev/null
@@ -1,17 +0,0 @@
----
-title:  Solaris Process Statistics
----
-
-Use these methods to get information about a Solaris operating system process that is using a Geode system.
-
-|                   |                                                                      |
-|-------------------|----------------------------------------------------------------------|
-| `imageSize`       | Size of the process image in megabytes.                              |
-| `rssSize`         | Size of the process resident set in megabytes.                       |
-| `userTime`        | Operating system statistic for the process CPU usage in user time.   |
-| `systemTime`      | Operating system statistic for the process CPU usage in system time. |
-| `processCpuUsage` | Operating system statistic for the CPU usage of this process.        |
-| `hostCpuUsage`    | Operating system statistic for the host CPU usage.                   |
-| `threads`         | Number of threads currently active in this process.                  |
-
-

http://git-wip-us.apache.org/repos/asf/geode-native/blob/87b6e035/geode-docs/docs/geode-native-docs/system-statistics/system_performance_statistics.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/docs/geode-native-docs/system-statistics/system_performance_statistics.html.md.erb b/geode-docs/docs/geode-native-docs/system-statistics/system_performance_statistics.html.md.erb
deleted file mode 100644
index 23c8e37..0000000
--- a/geode-docs/docs/geode-native-docs/system-statistics/system_performance_statistics.html.md.erb
+++ /dev/null
@@ -1,31 +0,0 @@
----
-title:  System Performance Statistics
----
-
-Performance statistics are collected for each application or cache server that connects to a distributed system.
-
--   **[Region Statistics](region_statistics.html)**
-
-    These methods help you to get the statistics of a region.
-
--   **[Cache Performance Statistics](cache_performance_statistics.html)**
-
-    Use cache performance statistics to determine the type and number of cache operations being performed and how much time they consume.
-
--   **[Continuous Query Statistics](continuous_query_statistics.html)**
-
-    Continuous query statistics give you information about a registered Continuous Query (CQ) represented by the CqQuery object.
-
--   **[CQ Service Statistics](cq_service_statistics.html)**
-
-    Use CQ service methods to get aggregate statistical information about the continuous queries of a client.
-
--   **[Pool Statistics](pool_statistics.html)**
-
-    Use the pool object to get statistics on connection pools.
-
--   **[Delta Statistics](delta_statistics.html)**
-
-    Delta statistics provide information about updates to data.
-
-

http://git-wip-us.apache.org/repos/asf/geode-native/blob/87b6e035/geode-docs/docs/geode-native-docs/system-statistics/windows_os_statistics.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/docs/geode-native-docs/system-statistics/windows_os_statistics.html.md.erb b/geode-docs/docs/geode-native-docs/system-statistics/windows_os_statistics.html.md.erb
deleted file mode 100644
index f247cd9..0000000
--- a/geode-docs/docs/geode-native-docs/system-statistics/windows_os_statistics.html.md.erb
+++ /dev/null
@@ -1,26 +0,0 @@
----
-title:  Windows Process Statistics
----
-
-Use these methods to get information about a Windows operating system process that is using a Geode system.
-
-|                       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
-|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| `handles`             | Total number of handles currently open by this process. This number is the sum of the handles currently open by each thread in this process.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
-| `priorityBase`        | Current base priority of the process. Threads within a process can raise and lower their own base priority relative to the process's base priority.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
-| `threads`             | Number of threads currently active in this process. An instruction is the basic unit of execution in a processor, and a thread is the object that executes instructions. Every running process has at least one thread.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| `activeTime`          | Elapsed time in milliseconds that all threads of this process used the processor to execute instructions. An instruction is the basic unit of execution in a computer, a thread is the object that executes instructions, and a process is the object created when a program is run. Code executed to handle some hardware interrupts and trap conditions are included in this count.                                                                                                                                                                                                                                                                                                                                                                                                          |
-| `pageFaults`          | Total number of page faults by the threads executing in this process. A page fault occurs when a thread refers to a virtual memory page that is not in its working set in main memory. This will not cause the page to be fetched from disk if it is on the standby list and hence already in main memory, or if it is in use by another process with whom the page is shared.                                                                                                                                                                                                                                                                                                                                                                                                                 |
-| `pageFileSize`        | Current number of bytes this process has used in the paging file(s). Paging files are used to store pages of memory used by the process that are not contained in other files. Paging files are shared by all processes, and lack of space in paging files can prevent other processes from allocating memory.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
-| `pageFileSizePeak`    | Maximum number of bytes this process has used in the paging file(s). Paging files are used to store pages of memory used by the process that are not contained in other files. Paging files are shared by all processes, and lack of space in paging files can prevent other processes from allocating memory.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
-| `privateSize`         | Current number of bytes this process has allocated that cannot be shared with other processes.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
-| `systemTime`          | Elapsed time in milliseconds that the threads of the process have spent executing code in privileged mode. When a Windows system service is called, the service often runs in Privileged Mode to gain access to system-private data. Such data is protected from access by threads executing in user mode. Calls to the system can be explicit or implicit, such as page faults or interrupts. Unlike some early operating systems, Windows uses process boundaries for subsystem protection in addition to the traditional protection of user and privileged modes. These subsystem processes provide additional protection. Therefore, some work done by Windows on behalf of your application might appear in other subsystem processes in addition to the privileged time in your process. |
-| `userTime`            | Elapsed time in milliseconds that this process's threads have spent executing code in user mode. Applications, environment subsystems, and integral subsystems execute in user mode. Code executing in User Mode cannot damage the integrity of the Windows Executive, Kernel, and device drivers. Unlike some early operating systems, Windows uses process boundaries for subsystem protection in addition to the traditional protection of user and privileged modes. These subsystem processes provide additional protection. Therefore, some work done by Windows on behalf of your application might appear in other subsystem processes in addition to the privileged time in your process.                                                                                             |
-| `virtualSize`         | Current size in bytes of the virtual address space the process is using. Use of virtual address space does not necessarily imply corresponding use of either disk or main memory pages. Virtual space is finite, and by using too much, the process can limit its ability to load libraries.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
-| `virtualSizePeak`     | Maximum number of bytes of virtual address space the process has used at any one time. Use of virtual address space does not necessarily imply corresponding use of either disk or main memory pages. Virtual space is however finite, and by using too much, the process might limit its ability to load libraries.                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| `workingSetSize`      | Current number of bytes in the Working Set of this process. The Working Set is the set of memory pages touched recently by the threads in the process. If free memory in the computer is above a threshold, pages are left in the Working Set of a process even if they are not in use. When free memory falls below a threshold, pages are trimmed from Working Sets. If pages are needed, they are then soft-faulted back into the Working Set before they are paged out to disk.                                                                                                                                                                                                                                                                                                            |
-| `workingSetSizePeak`  | Maximum number of bytes in the Working Set of this process at any point in time. The Working Set is the set of memory pages touched recently by the threads in the process. If free memory in the computer is above a threshold, pages are left in the Working Set of a process even if they are not in use. When free memory falls below a threshold, pages are trimmed from Working Sets. If they are needed they will then be soft faulted back into the Working Set before they leave main memory.                                                                                                                                                                                                                                                                                         |
-| `cpuUsage`            | Percentage CPU used by this process.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| `WindowsProcessStats` | Statistics for a Microsoft Windows process.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
-
-

http://git-wip-us.apache.org/repos/asf/geode-native/blob/87b6e035/geode-docs/docs/geode-native-docs/tools_modules/pulse/system_requirements.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/docs/geode-native-docs/tools_modules/pulse/system_requirements.html.md.erb b/geode-docs/docs/geode-native-docs/tools_modules/pulse/system_requirements.html.md.erb
deleted file mode 100644
index f770691..0000000
--- a/geode-docs/docs/geode-native-docs/tools_modules/pulse/system_requirements.html.md.erb
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title:  Pivotal GemFire Pulse System Requirements
----
-
-Verify that your system meets the installation and runtime requirements for GemFire Pulse.
-
-<a id="system_requirements__section_CBD5B04ACC554029B5C710CE8E244FEA"></a>
-The GemFire Pulse Web application has been tested for compatibility with the following Web browsers:
-
--   Internet Explorer 9.0.8112.16421
--   Safari 5.1.7 for Windows
--   Google Chrome 22.0.1229.79 m
--   Mozilla Firefox 16.0.1
-
-GemFire Pulse has been tested for standalone deployment on Tomcat and Jetty.
-GemFire Pulse may work with other operating systems and browsers upon which it has not been tested.
-
-

http://git-wip-us.apache.org/repos/asf/geode-native/blob/87b6e035/geode-docs/docs/geode-native-docs/tools_modules/vsd/vsd_system_requirements.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/docs/geode-native-docs/tools_modules/vsd/vsd_system_requirements.html.md.erb b/geode-docs/docs/geode-native-docs/tools_modules/vsd/vsd_system_requirements.html.md.erb
deleted file mode 100644
index d973e35..0000000
--- a/geode-docs/docs/geode-native-docs/tools_modules/vsd/vsd_system_requirements.html.md.erb
+++ /dev/null
@@ -1,38 +0,0 @@
----
-title:  VSD System Requirements
----
-
-View a list of platforms that are known to work with VSD.
-
-<a id="concept_9D005BF78EB7465DB735DB0755EE8EF8__section_1C59400B735448B18C2DEA7FD6365D2C"></a>
-The following platforms are known to work with the current VSD release:
-
--   RedHat 6
--   SLES 8
--   SLES 9
--   SLES 10
--   Mac OSX
--   Windows Server 2008
--   Windows 7 (Note: Requires slight modification; see below.)
-
-**64-Bit Platform Support**
-
-VSD is a 32-bit application. If you are running VSD on a 64-bit operating system, you may need to install 32-bit OS libraries to run the application if they are not already installed. On Linux, to find out which libraries are missing you can try running the following:
-
-``` pre
-ldd <product_dir>/tools/vsd/bin/vsdwishLinux
-```
-
-For 64-bit Windows, you can modify the scripts and executables as described in the note below.
-
-**Windows 7 and Later Support**
-
-To use VSD on Windows 7, perform the following steps:
-
-1.  Start Windows Explorer and navigate to the `GemFireProductDir\tools\vsd\bin\` directory (where *GemFireProductDir* corresponds to the location where you installed GemFire.)
-2.  Right click and select properties for vsd.bat.
-3.  Select the Compatibility tab.
-4.  Click "Run this program in compatibility mode for" and then select Windows XP SP3.
-5.  Repeat steps 2 and 3 for all the other executables in the `bin` directory.
-
-

http://git-wip-us.apache.org/repos/asf/geode-native/blob/87b6e035/geode-docs/docs/geode-native-docs/transactions/how-native-client-xacts-work.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/docs/geode-native-docs/transactions/how-native-client-xacts-work.html.md.erb b/geode-docs/docs/geode-native-docs/transactions/how-native-client-xacts-work.html.md.erb
deleted file mode 100644
index a2addf1..0000000
--- a/geode-docs/docs/geode-native-docs/transactions/how-native-client-xacts-work.html.md.erb
+++ /dev/null
@@ -1,38 +0,0 @@
----
-title:  How Native Client Transactions Work
----
-
-The syntax for writing client transactions is the same as with server or peer transactions, but when a client performs a transaction, the transaction is delegated to a server that brokers the transaction.
-
-## <a id="how-native-client-xacts-work__section_C804F1FE5BDF49CEA037AA589BBF284E" class="no-quick-link"></a>Role of Server Delegates in Transactions
-
-The Geode native client can run transactions on the Java cache server, using a server delegate to actually run the transaction code.
-
-For information on transaction requirements and activities on the server side, see [Transactions](geodeman/developing/transactions/chapter_overview.html).
-
-**Note:**
-The client cache blocks until the transaction is successfully committed. However, the client cache block is removed if the transaction is suspended.
-
-Depending on where the data resides, the server transaction delegate may or not be the same member that hosts the transaction. This is the same as for transactions run by the servers, but for server-run transactions, there is no delegate. There is just the member that is directly running its own transaction code.
-
-In this figure, the application code on the client makes changes to data entries Y and Z within a transaction. The server delegate that performs the transaction, M1, does not host the primary copy of the data being modified. The transaction takes place on server M2, where the data resides.
-
-<a id="how-native-client-xacts-work__fig_7E408D84E18C452683077528756E31C3"></a>
-<span class="figtitleprefix">Figure: </span>Transaction Run From a Client
-
-<img src="../common/images/xact-run-from-client.gif" id="how-native-client-xacts-work__image_E9ED33166A994014942ABAD9E6F61755" class="image" />
-
-To maintain cache consistency, the local client cache is not accessible during a transaction as it may reflect information inconsistent with the transaction in progress. When the transaction completes, the local cache is accessible again.
-
-In addition to the failure conditions common to all transactions, client transactions can also fail if the transaction delegate fails. If the delegate performing the transaction fails, the transaction code throws a `TransactionException`.
-
-## <a id="how-native-client-xacts-work__section_434BA87403C1449FADC3E7796E30F3C7" class="no-quick-link"></a>Native Client Transaction APIs
-
-The Geode API for distributed transactions has the familiar relational database methods, `begin`, `commit`, and `rollback`. There are also APIs available to suspend and resume transactions.
-
-The .NET classes for executing transactions are:
-
-**GemStone::GemFire::Cache::Generic**
-
--   CacheTransactionManager
--   TransactionId

http://git-wip-us.apache.org/repos/asf/geode-native/blob/87b6e035/geode-docs/docs/geode-native-docs/transactions/running-native-client-xact.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/docs/geode-native-docs/transactions/running-native-client-xact.html.md.erb b/geode-docs/docs/geode-native-docs/transactions/running-native-client-xact.html.md.erb
deleted file mode 100644
index 879b1cc..0000000
--- a/geode-docs/docs/geode-native-docs/transactions/running-native-client-xact.html.md.erb
+++ /dev/null
@@ -1,73 +0,0 @@
----
-title:  Running a Native Client Transaction
----
-
-Before you can run a native client transaction, you must configure your clients and servers; define your server regions for your transactions; and define your client regions.
-
-1.  Retrieve the Geode cache transaction manager.
-
-    **C++ example**
-
-    ``` pre
-    CacheTransactionManagerPtr txManager = 
-          cache->getCacheTransactionManager(); 
-    ```
-
-    **C\# .NET example**
-
-    ``` pre
-    CacheTransactionManager txManager =
-          cache.CacheTransactionManager;
-    ```
-
-2.  Run your transaction. (Detailed steps follow the examples.)
-
-    **C++ example**
-
-    ``` pre
-    TransactionIdPtr tid;
-    txManager->begin();
-    // ..do work
-    tid = txManager->suspend();
-    // following code can be run from another
-    // thread that has access to tid
-    try {
-      txManager->resume(tid);
-      // ..do work
-      tid = txManager->commit();
-    }  catch (const CommitConflictException& e) {
-      // ..on exception 
-    }
-    ```
-
-    **C\# .NET example**
-
-    ``` pre
-    TransactionId tid;
-    txManager.Begin();
-    // ..do work
-    tid = txManager.Suspend();
-    // following code can be run from another
-    // thread that has access to tid
-    try {
-      txManager.Resume(tid);
-      // ..do work
-      txManager.Commit();
-    } catch (CommitConflictException e)
-    ```
-    -   Start each transaction with a `begin` operation.
-    -   If your transaction runs on server regions that are a mix of partitioned and replicated regions, perform your first transaction operation on a partitioned region. This sets the server data host for the entire transaction. If you are using PR single-hop, single-hop will be applied as usual to this first operation.
-    -   Run the Geode operations and other operations that you want included in the transaction.
-    -   End each transaction with a `commit` or a `rollback`.
-        **Note:**
-        Do not leave any transaction in an uncommitted and unrolled back state unless you have suspended the transaction. Transactions that have not been explicitly suspended do not time out, so will remain in the system for the life of your application.
-
-3.  Review all of your client code for compatibility with transactions.
-
-When you commit a transaction, while the commit is taking place, the changes are visible in the cache. This is also known as transition commits. This provides better performance than locking everything to do the transaction updates, but it means that another process accessing data used in the transaction might get some data in the pre-transaction state and some in the post-transaction state.
-
-For example, keys 1 and 2 are written to in a transaction so both of their values change from A to B. In another thread, it is possible to read key 1 with value B and key 2 with value A, while the transaction is being committed. This can happen because of how Geode performs reads. This choice sacrifices atomic visibility in favor of performance. Reads do not block writes. Writes do not block reads.
-
-Because the client cache waits during transaction execution, and client regions are not distributed, the only activities that interact with a client transaction are those that occur on the server.
-
-

http://git-wip-us.apache.org/repos/asf/geode-native/blob/87b6e035/geode-docs/docs/geode-native-docs/transactions/suspend-resume-xacts.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/docs/geode-native-docs/transactions/suspend-resume-xacts.html.md.erb b/geode-docs/docs/geode-native-docs/transactions/suspend-resume-xacts.html.md.erb
deleted file mode 100644
index 64d7915..0000000
--- a/geode-docs/docs/geode-native-docs/transactions/suspend-resume-xacts.html.md.erb
+++ /dev/null
@@ -1,17 +0,0 @@
----
-title:  Suspending and Resuming Transactions
----
-
-The ability to suspend and resume transactions is useful when a thread must perform operations that should not be part of the transaction before the transaction can complete.
-
-When a transaction is suspended, it loses the transactional view of the cache. None of the previous operations (before calling suspend) are visible to the thread. Subsequently any operations that are performed by the thread do not participate in the suspended transaction.
-
-When a transaction is resumed, the resuming thread assumes the transactional view. A transaction that is suspending on a member must be resumed on the same member. Before resuming a transaction, you may want to check if the transaction exists on the member and whether it is suspended. You may optionally use the `tryResume` method.
-
-If the member with the primary copy of the data crashes, the transactional view that applied to that data is lost. The secondary member for the data cannot resume transactions suspended on the crashed member. You need to take remedial steps to retry the transaction on a new primary copy of the data.
-
-If a suspended transaction is not touched for a period of time, Geode cleans it up automatically. By default, the timeout for a suspended transaction is 30 minutes and can be configured by using the `suspended-tx-timeout` property of the `gfcpp.properties` file. The suspended transaction timeout value is specified in milliseconds.
-
-See [Running a Native Client Transaction](running-native-client-xact.html) for code examples of how to suspend and resume a transaction.
-
-

http://git-wip-us.apache.org/repos/asf/geode-native/blob/87b6e035/geode-docs/docs/geode-native-docs/transactions/transactions.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/docs/geode-native-docs/transactions/transactions.html.md.erb b/geode-docs/docs/geode-native-docs/transactions/transactions.html.md.erb
deleted file mode 100644
index 80229bb..0000000
--- a/geode-docs/docs/geode-native-docs/transactions/transactions.html.md.erb
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title:  Transactions
----
-
-*Transactions* describes how transactions work on the client side. It provides examples for running, suspending, and resuming transactions.
-
-Geode client transactions run on the server tier. The client uses a server delegate that runs the transaction as it would a local transaction. Thus, the key to running client transactions lies in making sure the server is properly configured and programmed. For complete information about Geode transactions in the Java server, see [Transactions](geodeman/developing/transactions/chapter_overview.html). It provides detailed information including server data requirements, interactions of Geode transactions with other operations running on the server tier, server-side application plug-ins with transactions, and querying with transactions.
-
--   **[How Native Client Transactions Work](how-native-client-xacts-work.html)**
-
-    The syntax for writing client transactions is the same as with server or peer transactions, but when a client performs a transaction, the transaction is delegated to a server that brokers the transaction.
-
--   **[Running a Native Client Transaction](running-native-client-xact.html)**
-
-    Before you can run a native client transaction, you must configure your clients and servers; define your server regions for your transactions; and define your client regions.
-
--   **[Suspending and Resuming Transactions](suspend-resume-xacts.html)**
-
-    The ability to suspend and resume transactions is useful when a thread must perform operations that should not be part of the transaction before the transaction can complete.

http://git-wip-us.apache.org/repos/asf/geode-native/blob/87b6e035/geode-docs/docs/geode-native-docs/type_mappings/chapter_overview.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/docs/geode-native-docs/type_mappings/chapter_overview.html.md.erb b/geode-docs/docs/geode-native-docs/type_mappings/chapter_overview.html.md.erb
deleted file mode 100644
index 2f2b58f..0000000
--- a/geode-docs/docs/geode-native-docs/type_mappings/chapter_overview.html.md.erb
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title:  Interoperability of Language Classes and Types
----
-
-*Interoperability of Language Classes and Types* provides a table that maps C++ class methods to corresponding .NET class methods and a table that maps Java types to .NET types.
-
--   **[C++ Class to .NET Class Mappings](cpp-class-to-dotnet-class-mappings.html)**
-
--   **[Java to .NET Type Mapping Table](java-to-dotnet-type-mapping.html)**
-
-
-
-

http://git-wip-us.apache.org/repos/asf/geode-native/blob/87b6e035/geode-docs/docs/geode-native-docs/type_mappings/cpp-class-to-dotnet-class-mappings.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/docs/geode-native-docs/type_mappings/cpp-class-to-dotnet-class-mappings.html.md.erb b/geode-docs/docs/geode-native-docs/type_mappings/cpp-class-to-dotnet-class-mappings.html.md.erb
deleted file mode 100644
index 3304112..0000000
--- a/geode-docs/docs/geode-native-docs/type_mappings/cpp-class-to-dotnet-class-mappings.html.md.erb
+++ /dev/null
@@ -1,169 +0,0 @@
----
-title:  C++ Class to .NET Class Mappings
----
-
-Wherever the native C++ class methods use pass-by-reference semantics to return data, the corresponding .NET methods shown in the following table return the object instead of using pass-by-reference semantics.
-
-<a id="concept_FD847E19497C4985ACB247C0FA2C2AD5__table_8D8D228E223E4E89A313A17DB5C38652"></a>
-
-<table>
-<caption><span class="tablecap">Table 1. C++ Class to .NET Class Mappings</span></caption>
-<colgroup>
-<col width="50%" />
-<col width="50%" />
-</colgroup>
-<thead>
-<tr class="header">
-<th><p>C++ Class</p></th>
-<th><p>.NET Class</p></th>
-</tr>
-</thead>
-<tbody>
-<tr class="odd">
-<td>class <code class="ph codeph">gemfire::AttributesFactory</code></td>
-<td>Sealed class <code class="ph codeph">AttributesFactory</code></td>
-</tr>
-<tr class="even">
-<td><p>class <code class="ph codeph">gemfire::AttributesMutator</code></p></td>
-<td>Sealed class <code class="ph codeph">AttributesMutator</code></td>
-</tr>
-<tr class="odd">
-<td>class <code class="ph codeph">gemfire::Cache</code></td>
-<td>Sealed class <code class="ph codeph">Cache</code></td>
-</tr>
-<tr class="even">
-<td><p>abstract class <code class="ph codeph">gemfire:: Cacheable</code></p></td>
-<td><p>Interface <code class="ph codeph">IPdxSerializable</code> or interface <code class="ph codeph">IGFSerializable</code></p></td>
-</tr>
-<tr class="odd">
-<td><p>class <code class="ph codeph">gemfire::CacheableBytes</code></p></td>
-<td><p><code class="ph codeph">Byte[]</code> or <code class="ph codeph">ArrayList&lt;Byte&gt;</code></p></td>
-</tr>
-<tr class="even">
-<td><p>class <code class="ph codeph">gemfire::Cacheableint32</code></p></td>
-<td><p><code class="ph codeph">Int32</code></p></td>
-</tr>
-<tr class="odd">
-<td><p>class <code class="ph codeph">gemfire:: CacheableString</code></p></td>
-<td><p><code class="ph codeph">String</code></p></td>
-</tr>
-<tr class="even">
-<td><p>abstract class <code class="ph codeph">gemfire:: CacheableKey</code></p></td>
-<td><p>You can use any type that implements <code class="ph codeph">hashcode</code> and <code class="ph codeph">equals</code>. The generic .NET built-in types are all suitable.</p></td>
-</tr>
-<tr class="odd">
-<td><p>abstract class <code class="ph codeph">gemfire::CacheListener</code></p></td>
-<td><p>Interface <code class="ph codeph">ICacheListener</code></p></td>
-</tr>
-<tr class="even">
-<td><p>class <code class="ph codeph">gemfire:: CacheLoader</code></p></td>
-<td><p>Interface <code class="ph codeph">ICacheLoader</code> plus static class <code class="ph codeph">CacheLoader</code></p></td>
-</tr>
-<tr class="odd">
-<td><p>class <code class="ph codeph">gemfire:: CacheWriter</code></p></td>
-<td><p>Interface class <code class="ph codeph">ICacheWriter</code></p></td>
-</tr>
-<tr class="even">
-<td><p>class <code class="ph codeph">gemfire::CacheFactory</code></p></td>
-<td><p>Sealed class <code class="ph codeph">CacheFactory</code></p></td>
-</tr>
-<tr class="odd">
-<td><p>class <code class="ph codeph">gemfire::DataInput</code></p></td>
-<td><p>With <code class="ph codeph">IPdxSerializable</code>, <code class="ph codeph">IPdxReader.</code></p>
-<p>With <code class="ph codeph">IGFSerializable</code>, sealed class <code class="ph codeph">DataInput</code>.</p></td>
-</tr>
-<tr class="even">
-<td><p>class <code class="ph codeph">gemfire:: DataOutput</code></p></td>
-<td><p>With <code class="ph codeph">IPdxSerializable</code>, <code class="ph codeph">IPdxWriter.</code></p>
-<p>With <code class="ph codeph">IGFSerializable</code>, sealed class <code class="ph codeph">DataOutput</code>.</p></td>
-</tr>
-<tr class="odd">
-<td><p>class <code class="ph codeph">gemfire:: DiskPolicyType</code></p></td>
-<td><p>enum <code class="ph codeph">DiskPolicyType</code> plus static class <code class="ph codeph">DiskPolicy</code> containing convenience methods for <code class="ph codeph">DiskPolicyType</code> enumeration</p></td>
-</tr>
-<tr class="even">
-<td><p>class <code class="ph codeph">gemfire:: DistributedSystem</code></p></td>
-<td><p>Sealed class <code class="ph codeph">DistributedSystem</code></p></td>
-</tr>
-<tr class="odd">
-<td><p>class <code class="ph codeph">gemfire:: EntryEvent</code></p></td>
-<td><p>Sealed class <code class="ph codeph">EntryEvent</code></p></td>
-</tr>
-<tr class="even">
-<td><p>class <code class="ph codeph">gemfire:: Exception</code></p></td>
-<td><p>Class <code class="ph codeph">GemfireException</code></p></td>
-</tr>
-<tr class="odd">
-<td><p>all other exceptions deriving from <code class="ph codeph">gemfire::                                     Exception</code></p></td>
-<td><p>Corresponding exceptions deriving from <code class="ph codeph">GemfireException</code></p></td>
-</tr>
-<tr class="even">
-<td><p>class <code class="ph codeph">gemfire:: ExpirationAction</code></p></td>
-<td><p>enum <code class="ph codeph">ExpirationAction</code> plus static class <code class="ph codeph">Expiration</code> containing convenience methods for <code class="ph codeph">ExpirationAction</code> enumeration</p></td>
-</tr>
-<tr class="odd">
-<td><p>class <code class="ph codeph">gemfire:: Log</code></p></td>
-<td><p>Static class <code class="ph codeph">Log</code>. The native <code class="ph codeph">Log::log</code> method is mapped to <code class="ph codeph">Log.Write</code> to avoid the conflict with the class name which is reserved for the constructors of Log class. The various loglevel <code class="ph codeph">Throw</code> or <code class="ph codeph">Catch</code> methods are not implemented, since they are redundant to <code class="ph codeph">Log::Log</code> , <code class="ph codeph">Log::LogThrow</code>, and <code class="ph codeph">Log::LogCatch</code> methods that take <code class="ph codeph">LogLevel</code> as a parameter.</p></td>
-</tr>
-<tr class="even">
-<td><p>enum <code class="ph codeph">gemfire:: MemberType</code></p></td>
-<td><p>enum <code class="ph codeph">MemberType</code></p></td>
-</tr>
-<tr class="odd">
-<td><p>abstract class <code class="ph codeph">gemfire:: PersistanceManager</code></p></td>
-<td><p>Not provided. You can register a C++ implementation using <code class="ph codeph">AttributesFactory.SetPersistenceManager</code> but you cannot implement a new one in .NET</p></td>
-</tr>
-<tr class="even">
-<td><p>class <code class="ph codeph">gemfire:: Properties</code></p></td>
-<td><p>Sealed class <code class="ph codeph">Properties</code></p></td>
-</tr>
-<tr class="odd">
-<td><p>class <code class="ph codeph">gemfire:: Properties::Visitor</code></p></td>
-<td><p>Delegate <code class="ph codeph">PropertiesVisitor</code></p></td>
-</tr>
-<tr class="even">
-<td><p>abstract class <code class="ph codeph">gemfire:: Region</code></p></td>
-<td><p>Class <code class="ph codeph">IRegion</code></p></td>
-</tr>
-<tr class="odd">
-<td><p>class <code class="ph codeph">gemfire:: RegionAttributes</code></p></td>
-<td><p>Sealed class <code class="ph codeph">RegionAttributes</code></p></td>
-</tr>
-<tr class="even">
-<td><p>class <code class="ph codeph">gemfire:: ScopeType</code></p></td>
-<td><p>enum <code class="ph codeph">ScopeType</code> plus static class <code class="ph codeph">Scope</code> containing convenience methods for <code class="ph codeph">ScopeType</code> enumeration+</p></td>
-</tr>
-<tr class="odd">
-<td><p>abstract class <code class="ph codeph">gemfire::                                     Serializable</code></p></td>
-<td><p>Two options:</p>
-<ul>
-<li><p>Interface <code class="ph codeph">IPdxSerializable</code></p></li>
-<li><p>Interface <code class="ph codeph">IGFSerializable</code> plus wrapper <code class="ph codeph">Serializable</code> class for native <code class="ph codeph">Serializable</code> and <code class="ph codeph">UserData</code> objects. The native <code class="ph codeph">toString</code> method is not provided, since the <code class="ph codeph">ToString</code> method of the base object class provides the same functionality.</p></li>
-</ul></td>
-</tr>
-<tr class="even">
-<td><p>class <code class="ph codeph">gemfire:: SystemProperties</code></p></td>
-<td><p>Sealed class <code class="ph codeph">SystemProperties</code></p></td>
-</tr>
-<tr class="odd">
-<td><p>class <code class="ph codeph">gemfire:: UserData</code></p></td>
-<td><p>Two options:</p>
-<ul>
-<li><p>Interface <code class="ph codeph">IPdxSerializable</code></p></li>
-<li><p>Interface <code class="ph codeph">IGFSerializable</code></p></li>
-</ul></td>
-</tr>
-<tr class="even">
-<td><p>class <code class="ph codeph">gemfire:: VectorT&lt;T&gt;</code></p></td>
-<td><p>Array of the given type, such as T[]</p></td>
-</tr>
-</tbody>
-</table>
-
-<span class="tablecap">Table 1. C++ Class to .NET Class Mappings</span>
-
--   **[Interoperability of C++ Types When Using PDX Serialization](../cpp-caching-api/type_interoperability.html)**
-
-    This topic table lists the mapping between C++ types and other language types when using PDX serialization.
-
-


Mime
View raw message