Red Hat SummitEste conteúdo não está disponível no idioma selecionado.
Chapter 2. Requirements for the Evaluated Configuration
2.1. Software Requirements
2.1.1. Operating System
A full range of platform tests have been performed on the following tested configurations.
| Operating System | Chipset Architecture | Java Virtual Machine |
|---|---|---|
| Red Hat Enterprise Linux 10 | x86_64 |
|
| Red Hat Enterprise Linux 9 | x86_64 |
|
| Red Hat Enterprise Linux 8 | x86_64 |
|
| Windows Server 2022 | x86_64 |
|
| Windows Server 2019 | x86_64 |
|
2.1.2. Database JDBC Drivers
JBoss EAP 8.1 is evaluated with the following relational database systems. Only these database systems with the specific driver versions are acceptable for use with JBoss EAP 8.1.
| Databases | JDBC Driver Versions |
|---|---|
| IBM DB2 Enterprise 12.1 | IBM DB2 JDBC Universal Driver Architecture 4.32.28 |
| Oracle 19c RAC | Oracle JDBC Driver v19.19.0.0 (ojdbc10.jar) |
| Oracle 23ai RAC | Oracle JDBC Driver v23.4.0.0.0 (ojdbc10.jar) |
| MySQL 8.4 | MySQL Connector/J 8.0.33 |
| MariaDB 11 | MariaDB Connector/J 3.1.4 |
| Microsoft SQL Server 2022 | Microsoft JDBC Drivers 12.4.1 (.jre11.jar) |
| PostgreSQL 17 | JDBC4 Postgresql Driver, Version 42.6.0 |
| EnterpriseDB Advanced Server 17.5 | Advanced Server JDBC Connector 42.5.4.1 |
| SAP ASE 16.1 | SAP JDBC driver 16.0 SP04 |
For information on how to configure each database with JBoss EAP 8.1, refer to Database Configuration.
2.1.3. LDAP Servers
JBoss EAP 8.1 is evaluated with the following LDAP servers. Only these LDAP servers are acceptable for use with JBoss EAP 8.1.
- Red Hat Directory Server 13.0
- Red Hat Directory Server 12.6
- Red Hat Directory Server 11.9
- Microsoft Active Directory 2022
- Microsoft Active Directory 2019
2.2. Physical Requirements
The hardware and software executing JBoss EAP 8.1, as well as the software critical to security policy enforcement must be protected from modification by unauthorized parties, whether internal or external. Reasonable physical security measures to ensure that unauthorized persons do not have physical access to the hardware running the JBoss EAP 8.1 software must be implemented.
2.3. Personnel Requirements
There must be one or more competent individuals who are assigned to manage JBoss EAP 8.1, its environment, and the security of the information it contains. The system administrator personnel must not be carelessly or willfully negligent, or hostile, and follow and abide by the instructions provided by the administrator documentation.
The developer of user applications executed by JBoss EAP 8.1, including web server applications and enterprise beans, must be trustworthy and comply with all instructions set forth by the user guidance and evaluated configuration guidance of JBoss EAP 8.1.
2.4. Connectivity Requirements
The operating system and the Java virtual machine operate according to their specification. These external systems shall be configured in accordance with this guidance.
Any other system with which JBoss EAP 8.1 communicates is assumed to be under the same management control and operate under the same security policy constraints as JBoss EAP 8.1.
2.4.1. Cluster Connectivity Requirements
JBoss EAP 8.1 instances must operate in a network segment that is logically separated from any other network segment by use of a packet filtering mechanism. This packet filter must only allow incoming communication that meets both the following criteria:
- The network protocol is TCP
- The destination port is 8080 or 8443
All outgoing communication from one of the JBoss EAP 8.1 instances must be allowed.
There are three defined interfaces to separate trusted and untrusted network traffic: public, cluster, and internal. Refer to Network Interfaces for more information.
Each cluster node communicates with the other nodes by means of standard network sockets. Whenever this occurs the client side of each connection has a port number assigned to it by the host operating system from a range of ports that are reserved for client sockets. These ports are referred to as dynamic or ephemeral ports. They are only used by a connection until it is closed. Once the connection is closed the port is made available for use by other new client connections. Refer to your operating system documentation if you need to configure this port range.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}