[GEODE-10518] blocks-2.0.0 : Update documentation for Jakarta EE 10 and Java 17

geode-book/config.yml

@@ -21,19 +21,19 @@ public_host: localhost
 sections:
 - repository:
     name: geode-docs
-  directory: docs/guide/115
+  directory: docs/guide/20
   subnav_template: geode-subnav
 
 template_variables:
   product_name_long: Apache Geode
   product_name: Geode
   product_name_lowercase: geode
-  product_version: '1.15'
-  product_version_nodot: '115'
-  product_version_old_minor: '1.14'
-  product_version_geode: '1.15'
-  min_java_version: '8'
-  min_java_update: '121'
+  product_version: '2.0'
+  product_version_nodot: '20'
+  product_version_old_minor: '1.15'
+  product_version_geode: '2.0'
+  min_java_version: '17'
+  min_java_update: '16'
   support_url: http://geode.apache.org/community
   product_url: http://geode.apache.org/
   book_title: Apache Geode Documentation

geode-book/master_middleman/source/subnavs/geode-subnav.erb

@@ -2147,26 +2147,6 @@ limitations under the License.
                             <li>
                                 <a href="/docs/guide/<%=vars.product_version_nodot%>/tools_modules/http_session_mgmt/configuring_non_sticky_sessions.html">Configuring Non-Sticky Sessions</a>
                             </li>
-                            <li class="has_submenu">
-                                <a href="/docs/guide/<%=vars.product_version_nodot%>/tools_modules/http_session_mgmt/session_mgmt_tcserver.html">HTTP Session Management Module for Pivotal tc Server</a>
-                                <ul>
-                                    <li>
-                                        <a href="/docs/guide/<%=vars.product_version_nodot%>/tools_modules/http_session_mgmt/tc_installing_the_module.html">Installing the HTTP Module for tc Server</a>
-                                    </li>
-                                    <li>
-                                        <a href="/docs/guide/<%=vars.product_version_nodot%>/tools_modules/http_session_mgmt/tc_setting_up_the_module.html">Setting Up the HTTP Module for tc Server</a>
-                                    </li>
-                                    <li class="has_submenu">
-                                        <a href="/docs/guide/<%=vars.product_version_nodot%>/tools_modules/http_session_mgmt/tc_changing_gf_default_cfg.html">Changing the Default Geode Configuration in the tc Server Module</a>
-                                        <ul>
-                                            <li>
-                                                <a href="/docs/guide/<%=vars.product_version_nodot%>/tools_modules/http_session_mgmt/interactive_mode_ref.html">Interactive Configuration Reference for the tc Server Module
-                                                </a>
-                                            </li>
-                                        </ul>
-                                    </li>
-                                </ul>
-                            </li>
                             <li class="has_submenu">
                                 <a href="/docs/guide/<%=vars.product_version_nodot%>/tools_modules/http_session_mgmt/session_mgmt_tomcat.html">HTTP Session Management Module for Tomcat</a>
                                 <ul>

geode-docs/configuring/cluster_config/persisting_configurations.html.md.erb

@@ -58,7 +58,7 @@ This section provides a walk-through example of configuring a simple <%=vars.pro
     Process ID: 70919
     Uptime: 12 seconds
     <%=vars.product_name%> Version: <%=vars.product_version%>
-    Java Version: 1.<%=vars.min_java_version%>.0_<%=vars.min_java_update%>
+    Java Version: <%=vars.min_java_version%>.0.<%=vars.min_java_update%>
     Log File: /Users/username/my_geode/locator1/locator1.log
     JVM Arguments: -Dgemfire.enable-cluster-configuration=true
     -Dgemfire.load-cluster-configuration-from-dir=false
@@ -84,7 +84,7 @@ This section provides a walk-through example of configuring a simple <%=vars.pro
     Process ID: 5627
     Uptime: 2 seconds
     <%=vars.product_name%> Version: <%=vars.product_version%>
-    Java Version: 1.<%=vars.min_java_version%>.0_<%=vars.min_java_update%>
+    Java Version: <%=vars.min_java_version%>.0.<%=vars.min_java_update%>
     Log File: /Users/username/my_geode/server1/server1.log
 
     JVM Arguments: -Dgemfire.default.locators=192.0.2.0[10334] -Dgemfire.groups=group1
@@ -100,7 +100,7 @@ This section provides a walk-through example of configuring a simple <%=vars.pro
     Process ID: 5634
     Uptime: 2 seconds
     <%=vars.product_name%> Version: <%=vars.product_version%>
-    Java Version: 1.<%=vars.min_java_version%>.0_<%=vars.min_java_update%>
+    Java Version: <%=vars.min_java_version%>.0.<%=vars.min_java_update%>
     Log File: /Users/username/my_geode/server2/server2.log
 
     JVM Arguments: -Dgemfire.default.locators=192.0.2.0[10334] -Dgemfire.groups=group1
@@ -117,7 +117,7 @@ This section provides a walk-through example of configuring a simple <%=vars.pro
     Process ID: 5637
     Uptime: 2 seconds
     <%=vars.product_name%> Version: <%=vars.product_version%>
-    Java Version: 1.<%=vars.min_java_version%>.0_<%=vars.min_java_update%>
+    Java Version: <%=vars.min_java_version%>.0.<%=vars.min_java_update%>
     Log File: /Users/username/my_geode/server3/server3.log
     JVM Arguments: -Dgemfire.default.locators=192.0.2.0[10334]
     -Dgemfire.start-dev-rest-api=false -Dgemfire.use-cluster-configuration=true
@@ -239,7 +239,7 @@ This section provides a walk-through example of configuring a simple <%=vars.pro
     Process ID: 5749
     Uptime: 15 seconds
     <%=vars.product_name%> Version: <%=vars.product_version%>
-    Java Version: 1.<%=vars.min_java_version%>.0_<%=vars.min_java_update%>
+    Java Version: <%=vars.min_java_version%>.0.<%=vars.min_java_update%>
     Log File: /Users/username/new_geode/locator2/locator2.log
 
     JVM Arguments: -Dgemfire.enable-cluster-configuration=true
@@ -276,7 +276,7 @@ This section provides a walk-through example of configuring a simple <%=vars.pro
     Process ID: 5813
     Uptime: 4 seconds
     <%=vars.product_name%> Version: <%=vars.product_version%>
-    Java Version: 1.<%=vars.min_java_version%>.0_<%=vars.min_java_update%>
+    Java Version: <%=vars.min_java_version%>.0.<%=vars.min_java_update%>
     Log File: /Users/username/new_geode/server4/server4.log
 
     JVM Arguments: -Dgemfire.default.locators=192.0.2.0[10335]
@@ -297,7 +297,7 @@ This section provides a walk-through example of configuring a simple <%=vars.pro
     Process ID: 5954
     Uptime: 2 seconds
     <%=vars.product_name%> Version: <%=vars.product_version%>
-    Java Version: 1.<%=vars.min_java_version%>.0_<%=vars.min_java_update%>
+    Java Version: <%=vars.min_java_version%>.0.<%=vars.min_java_update%>
     Log File: /Users/username/new_geode/server5/server5.log
     JVM Arguments: -Dgemfire.default.locators=192.0.2.0[10335] -Dgemfire.groups=group1
     -Dgemfire.start-dev-rest-api=false -Dgemfire.use-cluster-configuration=true

geode-docs/configuring/running/running_the_cacheserver.html.md.erb

@@ -147,12 +147,11 @@ If successful, the output provides information as in this sample:
 % gfsh status server --dir=server4
 Server in /home/username/server4 on 192.0.2.0[40404] as server4 is currently online.
 Process ID: 49008
-Uptime: 2 minutes 4 seconds
-<%=vars.product_name %> Version: <%=vars.product_version %>
-Java Version: 1.<%=vars.min_java_version%>.0_<%=vars.min_java_update%>
-Log File: /home/username/server4/server4.log
-JVM Arguments: 
-...
+Uptime: 2 seconds
+<%=vars.product_name%> Version: <%=vars.product_version%>
+Java Version: <%=vars.min_java_version%>.0.<%=vars.min_java_update%>
+Log File: /Users/username/my_geode/server1/server1.log
+JVM Arguments: -Dgemfire.default.locators=192.0.2.0[10334]
 ```
 
 ## <a id="running_the_cacheserver__section_0E4DDED6AB784B0CAFBAD538B227F487" class="no-quick-link"></a>Stop Server

geode-docs/configuring/running/running_the_locator.html.md.erb

@@ -203,7 +203,7 @@ Locator in /home/user/locator1 on ubuntu.local[10334] as locator1 is currently o
 Process ID: 2359
 Uptime: 17 minutes 3 seconds
 GemFire Version: 8.0.0
-Java Version: 1.<%=vars.min_java_version%>.0_<%=vars.min_java_update%>
+Java Version: <%=vars.min_java_version%>.0.<%=vars.min_java_update%>
 Log File: /home/user/locator1/locator1.log
 JVM Arguments: -Dgemfire.enable-cluster-configuration=true -Dgemfire.load-cluster-configuration-from-dir=false
  -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806

geode-docs/getting_started/15_minute_quickstart_gfsh.html.md.erb

@@ -54,12 +54,12 @@ The *locator* is a <%=vars.product_name%> process that tells new, connecting mem
     Process ID: 3529
     Uptime: 18 seconds
     <%=vars.product_name%> Version: <%=vars.product_version%>
-    Java Version: 1.<%=vars.min_java_version%>.0_<%=vars.min_java_update%>
+    Java Version: <%=vars.min_java_version%>.0.<%=vars.min_java_update%>
     Log File: /home/username/my_geode/locator1/locator1.log
     JVM Arguments: -Dgemfire.enable-cluster-configuration=true -Dgemfire.load-cluster-configuration-from-dir=false
     -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true
     -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
-    Class-Path: /home/username/Apache_Geode_Linux/lib/geode-core-1.0.0.jar:
+    Class-Path: /home/username/Apache_Geode_Linux/lib/geode-core-2.0.0.jar:
     /home/username/Apache_Geode_Linux/lib/geode-dependencies.jar
 
     Successfully connected to: JMX Manager [host=10.118.33.169, port=1099]
@@ -413,12 +413,12 @@ In this step you restart the cache servers in parallel. Because the data is pers
     Process ID: 3402
     Uptime: 1 minute 46 seconds
     <%=vars.product_name%> Version: <%=vars.product_version%>
-    Java Version: 1.<%=vars.min_java_version%>.0_<%=vars.min_java_update%>
+    Java Version: <%=vars.min_java_version%>.0.<%=vars.min_java_update%>
     Log File: /home/username/my_geode/server1/server1.log
     JVM Arguments: -Dgemfire.default.locators=192.0.2.0[10334] -Dgemfire.use-cluster-configuration=true
     -XX:OnOutOfMemoryError=kill -KILL %p -Dgemfire.launcher.registerSignalHandlers=true
     -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
-    Class-Path: /home/username/Apache_Geode_Linux/lib/geode-core-1.0.0.jar:
+    Class-Path: /home/username/Apache_Geode_Linux/lib/geode-core-2.0.0.jar:
     /home/username/Apache_Geode_Linux/lib/geode-dependencies.jar
     ```
 

geode-docs/getting_started/installation/install_standalone.html.md.erb

@@ -24,7 +24,7 @@ Build from source or use the TAR distribution to install <%=vars.product_name_lo
 1.  Set the JAVA\_HOME environment variable.
 
     ``` pre
-    JAVA_HOME=/usr/java/jdk1.<%=vars.min_java_version%>.0_<%=vars.min_java_update%>
+    JAVA_HOME=/usr/java/jdk-<%=vars.min_java_version%>.0.<%=vars.min_java_update%>
     export JAVA_HOME
     ```
 
@@ -54,7 +54,7 @@ Build from source or use the TAR distribution to install <%=vars.product_name_lo
 1.  Set the JAVA\_HOME environment variable. For example:
 
     ``` pre
-    $ set JAVA_HOME="C:\Program Files\Java\jdk1.<%=vars.min_java_version%>.0_<%=vars.min_java_update%>" 
+    $ set JAVA_HOME="C:\Program Files\Java\jdk-<%=vars.min_java_version%>.0.<%=vars.min_java_update%>" 
     ```
 
 2.  Install Gradle, version 2.3 or a more recent version.
@@ -91,14 +91,14 @@ Build from source or use the TAR distribution to install <%=vars.product_name_lo
 3.  Set the JAVA\_HOME environment variable. On Linux/Unix platforms:
 
     ``` pre
-    JAVA_HOME=/usr/java/jdk1.<%=vars.min_java_version%>.0_<%=vars.min_java_update%>
+    JAVA_HOME=/usr/java/jdk-<%=vars.min_java_version%>.0.<%=vars.min_java_update%>
     export JAVA_HOME
     ```
 
     On Windows platforms:
 
     ``` pre
-    set JAVA_HOME="C:\Program Files\Java\jdk1.<%=vars.min_java_version%>.0_<%=vars.min_java_update%>"
+    set JAVA_HOME="C:\Program Files\Java\jdk-<%=vars.min_java_version%>.0.<%=vars.min_java_update%>"
     ```
 
 4.  Add the <%=vars.product_name%> scripts to your PATH environment variable. On Linux/Unix platforms:

geode-docs/managing/management/jmx_manager_operations.html.md.erb

@@ -57,7 +57,7 @@ is currently online.
 Process ID: 27144
 Uptime: 5 seconds
 <%=vars.product_name%> Version: <%=vars.product_version%>
-Java Version: 1.<%=vars.min_java_version%>.0_<%=vars.min_java_update%>
+Java Version: <%=vars.min_java_version%>.0.<%=vars.min_java_update%>
 Log File: /Users/username/apache-geode/locator1/locator1.log
 JVM Arguments: -Dgemfire.enable-cluster-configuration=true 
 -Dgemfire.load-cluster-configuration-from-dir=false 

geode-docs/tools_modules/gfsh/tour_of_gfsh.html.md.erb

@@ -61,7 +61,7 @@ as locator1 is currently online.
 Process ID: 67666
 Uptime: 6 seconds
 <%=vars.product_name%> Version: <%=vars.product_version%>
-Java Version: 1.<%=vars.min_java_version%>.0_<%=vars.min_java_update%>
+Java Version: <%=vars.min_java_version%>.0.<%=vars.min_java_update%>
 Log File: /home/username/gfsh_tutorial/locator1.log
 JVM Arguments: -Dgemfire.enable-cluster-configuration=true
  -Dgemfire.load-cluster-configuration-from-dir=false
@@ -180,16 +180,12 @@ Starting a <%=vars.product_name%> Server in /home/username/gfsh_tutorial/server1
 ...
 Server in /home/username/gfsh_tutorial/server1 on 192.0.2.0[40404] as server1
 is currently online.
-Process ID: 68375
-Uptime: 4 seconds
+Process ID: 49601
+Uptime: 2 seconds
 <%=vars.product_name%> Version: <%=vars.product_version%>
-Java Version: 1.<%=vars.min_java_version%>.0_<%=vars.min_java_update%>
-Log File: /home/username//gfsh_tutorial/server1/server1.log
-JVM Arguments: -Dgemfire.locators=localhost[10334]
- -Dgemfire.use-cluster-configuration=true -Dgemfire.start-dev-rest-api=false
- -XX:OnOutOfMemoryError=kill -KILL %p
- -Dgemfire.launcher.registerSignalHandlers=true
- -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
+Java Version: <%=vars.min_java_version%>.0.<%=vars.min_java_update%>
+Log File: /home/username/gfsh_tutorial/server1/server1.log
+JVM Arguments: -Dgemfire.enable-cluster-configuration=true
 Class-Path: /home/username/geode/geode-assembly/build/install/apache-geode/lib
 /geode-core-1.2.0.jar:/home/username/geode/geode-assembly/build/install
 /apache-geode/lib/geode-dependencies.jar
@@ -299,7 +295,7 @@ server2 is currently online.
 Process ID: 68423
 Uptime: 4 seconds
 <%=vars.product_name%> Version: <%=vars.product_version%>
-Java Version: 1.<%=vars.min_java_version%>.0_<%=vars.min_java_update%>
+Java Version: <%=vars.min_java_version%>.0.<%=vars.min_java_update%>
 Log File: /home/username/gfsh_tutorial/server2/server2.log
 JVM Arguments: -Dgemfire.default.locators=192.0.2.0[10334]
  -Dgemfire.use-cluster-configuration=true -Dgemfire.start-dev-rest-api=false

geode-docs/tools_modules/http_session_mgmt/chapter_overview.html.md.erb

@@ -21,7 +21,9 @@ limitations under the License.
 
 The <%=vars.product_name_long%> HTTP Session Management modules provide fast, scalable, and reliable session replication for HTTP servers without requiring application changes.
 
-<%=vars.product_name_long%> offers HTTP session management modules for tc Server, Tomcat, and AppServers.
+<%=vars.product_name_long%> offers HTTP session management modules for Tomcat and AppServers.
+
+**Note:** As of version 2.x, Geode only supports Tomcat 10.1 and later versions (Jakarta EE namespace). Support for Tomcat 7, 8, 9, and Pivotal tc Server has been discontinued.
 
 These modules are included with the <%=vars.product_name_long%> product distribution, and installation .zip files can be found in the `tools/Modules` directory of your product installation.
 
@@ -49,13 +51,9 @@ These modules are included with the <%=vars.product_name_long%> product distribu
 
     This section describes the configuration of non-sticky sessions.
 
--   **[HTTP Session Management Module for Pivotal tc Server](../../tools_modules/http_session_mgmt/session_mgmt_tcserver.html)**
-
-    This section describes how to set up and use the HTTP session management module with tc Server templates.
-
 -   **[HTTP Session Management Module for Tomcat](../../tools_modules/http_session_mgmt/session_mgmt_tomcat.html)**
 
-    You set up and use the module by modifying the Tomcat's `server.xml` and `context.xml` files.
+    You set up and use the module by modifying Tomcat's `server.xml` and `context.xml` files. Supports Tomcat 10.1 and later (Jakarta EE).
 
 -   **[HTTP Session Management Module for AppServers](../../tools_modules/http_session_mgmt/session_mgmt_weblogic.html)**
 

geode-docs/tools_modules/http_session_mgmt/common_gemfire_topologies.html.md.erb

@@ -33,4 +33,4 @@ In a peer-to-peer configuration, each instance within an application server cont
 
 <img src="../../images_svg/http_module_cs_with_locator.svg" id="common_gemfire_topologies__image_oss_zyw_rv" class="image" />
 
-In a client/server configuration, the Tomcat or tc Server instance operates as a <%=vars.product_name%> client, which must communicate with one or more <%=vars.product_name%> servers to acquire session data. The client maintains its own local cache and will communicate with the server to satisfy cache misses. A client/server configuration is useful when you want to separate the application server instance from the cached session data. In this configuration, you can reduce the memory consumption of the application server since session data is stored in separate <%=vars.product_name%> server processes.
+In a client/server configuration, the Tomcat instance operates as a <%=vars.product_name%> client, which must communicate with one or more <%=vars.product_name%> servers to acquire session data. The client maintains its own local cache and will communicate with the server to satisfy cache misses. A client/server configuration is useful when you want to separate the application server instance from the cached session data. In this configuration, you can reduce the memory consumption of the application server since session data is stored in separate <%=vars.product_name%> server processes.