Skip to content

Docs: set supported Java and Tomcat versions #944

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
maximthomas merged 4 commits into from
Dec 10, 2025
Merged

Docs: set supported Java and Tomcat versions #944

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
98dcd7d
Docs: set supported Java and Tomcat versions
maximthomas Dec 3, 2025
816c0f0
Update J2EE Agent Tomcat Installation docs
maximthomas Dec 4, 2025
7f58410
Update J2EE Agent Jetty installation docs
maximthomas Dec 4, 2025
e822394
remove outdated docs for J2EE agent
maximthomas Dec 8, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion ...umentation/openam-doc-source/src/main/asciidoc/admin-guide/chap-monitoring.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -106,7 +106,7 @@ You can also browse the MBeans by connecting to your web application container,

[#figure-jconsole-to-openam]
image::images/jconsole-to-openam.png[]
Also see link:http://docs.oracle.com/javase/1.5.0/docs/guide/management/agent.html[Monitoring and Management Using JMX, window=\_blank] for instructions on how to connect remotely, how to use SSL, and so forth.
Also see link:https://docs.oracle.com/en/java/javase/11/management/monitoring-and-management-using-jmx-technology.html[Monitoring and Management Using JMX Technology, window=\_blank] for instructions on how to connect remotely, how to use SSL, and so forth.

[IMPORTANT]
====
Expand Down
6 changes: 3 additions & 3 deletions openam-documentation/openam-doc-source/src/main/asciidoc/admin-guide/chap-sts.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1501,7 +1501,7 @@ Deploy the `.war` file as follows:
. OpenAM supports the following web containers for SOAP STS deployments:
+

* Apache Tomcat 6, 7, or 8
* Apache Tomcat 10.1.x or 11

* Jetty 7, 8, or 9

Expand Down Expand Up @@ -1609,13 +1609,13 @@ Then, you can make the following changes:
[#sts-soap-logger]
==== Configuring the SOAP STS Logger

OpenAM SOAP STS logs to the Simple Logging Facade for Java (SLF4J) API. Because the Apache CXF framework, by default, logs to the `java.util.logging` object, the OpenAM SOAP STS is built with a maven dependency upon `slf4j-jdk14`, which allows OpenAM SOAP STS log entries to be configured via `java.util.logging`. As a result, you can implement both OpenAM SOAP STS and Apache CXF logging to be configured via the `logging.properties` file in the Tomcat `conf` directory.
OpenAM SOAP STS logs to the Simple Logging Facade for Java (SLF4J) API. Because the Apache CXF framework, by default, logs to the `java.util.logging` object, the OpenAM SOAP STS is built with a maven dependency upon `slf4j`, which allows OpenAM SOAP STS log entries to be configured via `java.util.logging`. As a result, you can implement both OpenAM SOAP STS and Apache CXF logging to be configured via the `logging.properties` file in the Tomcat `conf` directory.

You can configure and customize Apache CXF-related logging according to directions given at the following web site: link:http://cxf.apache.org/docs/debugging-and-logging.html[http://cxf.apache.org/docs/debugging-and-logging.html, window=\_blank]

[NOTE]
====
Because the OpenAM SOAP STS code logs to the SLF4J API, the manner in which these logs are realized is a function of the jar file state bundled in the OpenAM SOAP STS server `.war` file. If you implement the OpenAM SOAP STS logs using a different framework, you can replace the `slf4j-jdk14` Maven dependency in the OpenAM SOAP STS server `pom.xml` file by the desired dependency and rebuild the `.war` file. Or you can change the generated OpenAM SOAP STS server `.war` file to include the desired `.jar` file, which will realize the SLF4J API with the desired logging framework.
Because the OpenAM SOAP STS code logs to the SLF4J API, the manner in which these logs are realized is a function of the jar file state bundled in the OpenAM SOAP STS server `.war` file. If you implement the OpenAM SOAP STS logs using a different framework, you can replace the `slf4j` Maven dependency in the OpenAM SOAP STS server `pom.xml` file by the desired dependency and rebuild the `.war` file. Or you can change the generated OpenAM SOAP STS server `.war` file to include the desired `.jar` file, which will realize the SLF4J API with the desired logging framework.

Also, note that the `debugfiles.properties` included in the OpenAM SOAP STS server `.war` file does not configure logging. It is present only because some OpenAM code leveraged by the SOAP STS continues to have dependencies upon the legacy, OpenAM debug logger. The presence of this file minimizes the number of harmless error logs generated by the initialization of this legacy debug logger. OpenAM SOAP STS does not utilize this logger.
====
Expand Down
4 changes: 2 additions & 2 deletions ...nam-doc-source/src/main/asciidoc/deployment-planning/chap-high-level-start.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -329,9 +329,9 @@ The installation process requires that you implement your deployment plan.

* *Prepare the Operating System*. Prepare your operating system, depending on the OS: Linux, Solaris, Windows, Cloud (Amazon EC2, OpenStack, and so forth), Virtual Machines (VMWare, Xen, Hyper-V, and so forth)

* *Prepare the Java Environment*. Prepare your Java environment, depending on your vendor type: Oracle, IBM, OpenJDK.
* *Prepare the Java Environment*. Prepare your Java environment, depending on your vendor type: Oracle, OpenJDK, Eclipse Temurin etc.

* *Prepare the App Server*. Prepare your application server, depending on type: Apache Tomcat, JBoss 4/5, WildFly, Jetty, Oracle WebLogic, IBM WebSphere. Also, prepare each app server for HTTPS.
* *Prepare the App Server*. Prepare your application server, depending on type: Apache Tomcat, Jetty, Oracle WebLogic, IBM WebSphere. Also, prepare each app server for HTTPS.

* *Prepare the Directory Servers*. Prepare the configuration directory server, OpenDJ for the core token service (CTS), and the LDAP identity repository. For information on installing data repositories, see xref:../install-guide/chap-prepare-install.adoc#chap-prepare-install["Preparing For Installation"] in the __Installation Guide__.

Expand Down
17 changes: 7 additions & 10 deletions ...m-doc-source/src/main/asciidoc/deployment-planning/chap-hw-sw-requirements.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -182,11 +182,8 @@ a|2008, 2008 R2, 2012, 2012 R2
|===
|Vendor |Version

a|Oracle JDK
a|7, 8

a|IBM SDK, Java Technology Edition (Websphere only)
a|7
a|Any JDK vendor, i.e. Oracle JDK, Eclipse Temurin, Amazon Coretto
a|11 LTS or later
|===


Expand All @@ -201,7 +198,7 @@ a|7
|Web Container |Version

a|Apache Tomcat
a|7, 8
a|10.1.X, 11

a|Oracle WebLogic Server
a|12c
Expand Down Expand Up @@ -341,7 +338,7 @@ a|[none]
a|[none]
* 5, 6, 7
a|[none]
* Apache Tomcat 6, 7, 8
* Apache Tomcat 10.1.X, 11
* IBM Web Sphere Application Server 8, 8.5
* JBoss Enterprise Application Platform 6
* JBoss Application Server 7
Expand All @@ -353,23 +350,23 @@ a|[none]
a|[none]
* 2008, 2008 R2, 2012, 2012 R2
a|[none]
* Apache Tomcat 6, 7, 8
* Apache Tomcat 10.1.X, 11

a|[none]
* Oracle Solaris x64
* Oracle Solaris SPARC
a|[none]
* 10, 11
a|[none]
* Apache Tomcat 6, 7, 8
* Apache Tomcat 10.1.X, 11
* Oracle WebLogic Server 11g, 12c

a|[none]
* Ubuntu Linux
a|[none]
* 12.04 LTS, 14.04 LTS
a|[none]
* Apache Tomcat 6, 7, 8
* Apache Tomcat 10.1.X, 11
* IBM Web Sphere Application Server 8, 8.5
* JBoss Enterprise Application Platform 6
* JBoss Application Server 7
Expand Down
5 changes: 1 addition & 4 deletions ...ntation/openam-doc-source/src/main/asciidoc/deployment-planning/chap-intro.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -172,7 +172,4 @@ In February 2010, a small group of former Sun employees founded ForgeRock to con

* 2016: OpenAM 14

* 2025: OpenAM 15



* 2025: OpenAM 15 and 16
4 changes: 2 additions & 2 deletions ...ion/openam-doc-source/src/main/asciidoc/install-guide/chap-prepare-install.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,7 @@ Check the effective top-level domain list at link:https://publicsuffix.org/list/
[#prepare-java]
=== Preparing a Java Environment

OpenAM software depends on a Java runtime environment. Check the output of `java -version` to make sure your the version is supported. The current OpenAM release supports Java Development Kit 8, 11, 17 or 21 LTS version.
OpenAM software depends on a Java runtime environment. Check the output of `java -version` to make sure your the version is supported. The current OpenAM release supports Java Development Kit 11, 17, 21 or 25 LTS version.

[#prepare-java-sun]
==== Settings For Sun/Oracle Java Environments
Expand Down Expand Up @@ -1355,7 +1355,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 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 JDK 11 LTS or later.

[source, shell]
----
Expand Down
Loading