Docs: Drop JDK 7 support and remove MetaspaceSize options (#838)

Author: maximthomas

openam-documentation/openam-doc-source/src/main/asciidoc/admin-guide/chap-tuning.adoc

@@ -12,7 +12,7 @@
   information: "Portions copyright [year] [name of copyright owner]".
 
   Copyright 2017 ForgeRock AS.
-  Portions Copyright 2024 3A Systems LLC.
+  Portions Copyright 2024-2025 3A Systems LLC.
 ////
 
 :figure-caption!:
@@ -254,14 +254,6 @@ a|`-server`
 a|-
 a|Ensures the server JVM is used
 
-a|`-XX:PermSize` & `-XX:MaxPermSize` (JDK 7)
-a|Set both to 256 MB
-a|Controls the size of the permanent generation in the JVM
-
-a|`-XX:MetaspaceSize` & `-XX:MaxMetaspaceSize` (JDK 8)
-a|Set both to 256 MB
-a|Controls the size of the metaspace in the JVM
-
 a|`-Dsun.net.client.defaultReadTimeout`
 a|60000
 a|Controls the read timeout in the Java HTTP client implementation

openam-documentation/openam-doc-source/src/main/asciidoc/deployment-planning/chap-hw-sw-requirements.adoc

@@ -127,7 +127,7 @@ Check your assumptions in testing. For example, make sure that logs are cleaned
 [#ram-requirements]
 ==== Random Access Memory Requirements
 
-OpenAM core services require a minimum JVM heap size of 1 GB and, when running on JDK 7, a minimum permanent generation size of 256 MB. If you are including the embedded OpenDJ directory, OpenAM requires at least a 2 GB heap, as 50% of that space is allocated to OpenDJ.
+OpenAM core services require a minimum JVM heap size of 1 GB and. If you are including the embedded OpenDJ directory, OpenAM requires at least a 2 GB heap, as 50% of that space is allocated to OpenDJ.
 
 [NOTE]
 ====

openam-documentation/openam-doc-source/src/main/asciidoc/install-guide/chap-prepare-install.adoc

@@ -57,26 +57,11 @@ OpenAM software depends on a Java runtime environment. Check the output of `java
 ==== Settings For Sun/Oracle Java Environments
 
 --
-When using a Sun or Oracle Java environment set at least the following options.
+When using an Adoptium, Azul or Oracle Java environment set at least the following options.
 
 `-server`::
 Use `-server` rather than `-client`.
 
-`-Xmx1g` (minimum)::
-OpenAM requires at least a 1 GB heap. If you are including the embedded OpenDJ directory, OpenAM requires at least a 2 GB heap, as 50% of that space is allocated to OpenDJ. Higher volume and higher performance deployments require additional heap space.
-
-`-XX:PermSize=256m` (when using JDK 7)::
-Set the permanent generation size to 256 MB.
-
-`-XX:MaxPermSize=256m` (when using JDK 7)::
-Set the maximum permanent generation size to 256 MB.
-
-`-XX:MetaspaceSize=256m` (when using JDK 8)::
-Set the metaspace memory size to 256 MB.
-
-`-XX:MaxMetaspaceSize=256m` (when using JDK 8)::
-Set the maximum metaspace memory size to 256 MB.
-
 
 [IMPORTANT]
 ====
@@ -107,9 +92,6 @@ When using an IBM Java environment set at least the following options.
 `-DamCryptoDescriptor.provider=IBMJCE`,`-DamKeyGenDescriptor.provider=IBMJCE`::
 Use the IBM Java Cryptography Extensions.
 
-`-Xmx1024m` (minimum)::
-OpenAM requires at least a 1 GB heap. If you are including the embedded OpenDJ directory, OpenAM requires at least a 2 GB heap, as 50% of that space is allocated to OpenDJ. Higher volume and higher performance deployments require additional heap space.
-
 --
 
 
@@ -1377,7 +1359,7 @@ You should also ensure `sslProtocol` is set to `TLS`, which disables the potenti
               maxThreads="150" scheme="https" secure="true"
               clientAuth="false" sslProtocol="TLS" URIEncoding="UTF-8" />
 ----
-The following example script, `/etc/init.d/tomcat`, manages the service at system startup and shutdown. This script assumes you run OpenAM as the user `openam` and that you use Oracle JDK 7.
+The following example script, `/etc/init.d/tomcat`, manages the service at system startup and shutdown. This script assumes you run OpenAM as the user `openam` and that you use Oracle JDK 8.
 
 [source, shell]
 ----
@@ -1391,7 +1373,7 @@ CATALINA_HOME="/path/to/tomcat"
 export CATALINA_HOME
 JAVA_HOME=/path/to/jdk
 export JAVA_HOME
-CATALINA_OPTS="-server -Xmx2g -XX:MetaspaceSize=256m -XX:MaxMetaspaceSize=256m"
+CATALINA_OPTS="-server"
 export CATALINA_OPTS
 
 case "${1}" in
@@ -1417,7 +1399,7 @@ One possible workaround is to configure Tomcat to allow encoded slash characters
 
 [source]
 ----
-CATALINA_OPTS= "-server -Xmx2g -XX:MetaspaceSize=256m -XX:MaxMetaspaceSize=256m \
+CATALINA_OPTS= "-server \
                -Dorg.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH=true"
 ----
 
@@ -1485,10 +1467,6 @@ After configuring JBoss or WildFly, you then prepare OpenAM for deployment by ma
 .. Open the `standalone.conf` file in the `/path/to/jboss/bin` directory for JBoss or WildFly in standalone mode.
 
 .. Check the JVM settings associated with `JAVA_OPTS`.
-+
-Change the JVM heap size to `-Xmx1024m`. The default JVM heap size for some versions of JBoss might already exceed the recommended value. If you are using the embedded version of OpenDJ, the minimum heap size may be higher. For details on the JVM options to use, see xref:#prepare-java["Preparing a Java Environment"].
-+
-Change the metaspace size to `-XX:MaxMetaspaceSize=256m` if the default size does not exceed this amount.
 
 .. Set the following JVM `JAVA_OPTS` setting in the same file:
 +