Chapter 2. Before You Begin
2.1. The difference between Red Hat JBoss Web Server and JWS for OpenShift
The differences between the JWS for OpenShift images and the regular release of JWS are:
The location of
JWS_HOMEinside a JWS for OpenShift image is:
- All load balancing is handled by the OpenShift router, not Apache HTTP Server mod_cluster or mod_jk connectors.
Documentation for JWS functionality not specific to JWS for OpenShift images is found in the Red Hat JBoss Web Server documentation.
2.2. Version compatibility and support
See the xPaaS table on the OpenShift Container Platform Tested 3.X Integrations page and OpenShift Container Platform Tested 4.X Integrations page for details about OpenShift image version compatibility.
The 5.4 version of JWS for OpenShift images and application templates should be used for deploying new applications.
The 5.3 version of JWS for OpenShift images and application templates are deprecated and no longer receives updates.
2.3. Supported Architectures by JBoss Web Server
JBoss Web server supports the following architectures:
- x86_64 (AMD64)
- IBM Z (s390x) in the OpenShift environment
- IBM Power (ppc64le) in the OpenShift environment
Different images are supported for different architectures. The example codes in this guide demonstrate the commands for x86_64 architecture. If you are using other architectures, specify the relevant image name in the commands. See the Red Hat Container Catalog for more information about images.
2.4. Health checks for Red Hat container images
All container images available for OpenShift have a health rating associated with it. You can find the health rating for Red Hat JBoss Web Server by navigating to the catalog of container images, searching for
JBoss Web Server and selecting the 5.4 version.
For more information on how OpenShift container can be tested for liveliness and readiness, please refer to the following documentation