Chapter 1. Introduction 1.1. What is Red Hat JBoss Enterprise Application Platform (JBoss EAP)? Red Hat JBoss Enterprise Application Platform 7.4 (JBoss EAP) is a middleware platform built on open standards and compliant with the Jakarta EE 8 specification. It provides preconfigured options for features such as high-availability clustering, messaging, and distributed caching. It includes a modular structure that allows you to enable services only when required, which results in improved startup speed. The web-based management console and management command line interface (CLI) make editing XML configuration files unnecessary and add the ability to script and automate tasks. In addition, JBoss EAP includes APIs and development frameworks that allow you to quickly develop, deploy, and run secure and scalable Jakarta EE applications. JBoss EAP 7.4 is a Jakarta EE 8 compatible implementation for both Web Profile and Full Platform specifications. 1.2. How Does JBoss EAP Work on OpenShift? Red Hat offers a containerized image for JBoss EAP that is designed for use with OpenShift. Using this image, developers can quickly and easily build, scale, and test applications that are deployed across hybrid environments. 1.3. Comparison: JBoss EAP and JBoss EAP for OpenShift There are some notable differences when comparing the JBoss EAP product with the JBoss EAP for OpenShift image. The following table describes these differences and notes which features are included or supported in the current version of JBoss EAP for OpenShift. Table 1.1. Differences between JBoss EAP and JBoss EAP for OpenShift JBoss EAP Feature Status in JBoss EAP for OpenShift Description JBoss EAP management console Not included The JBoss EAP management console is not included in this release of JBoss EAP for OpenShift. JBoss EAP management CLI Not recommended The JBoss EAP management CLI is not recommended for use with JBoss EAP running in a containerized environment. Any configuration changes made using the management CLI in a running container will be lost when the container restarts. The management CLI is accessible from within a pod for troubleshooting purposes . Managed domain Not supported Although a JBoss EAP managed domain is not supported, creation and distribution of applications are managed in the containers on OpenShift. Default root page Disabled The default root page is disabled, but you can deploy your own application to the root context as ROOT.war . Remote messaging Supported Red Hat AMQ for inter-pod and remote messaging is supported. ActiveMQ Artemis is only supported for messaging within a single pod with JBoss EAP instances, and is only enabled when Red Hat AMQ is absent. Transaction recovery Partially supported The EAP operator is the only tested and supported option of transaction recovery in OpenShift 4. For more information about recovering transactions using the EAP operator, see EAP Operator for Safe Transaction Recovery . Some scenarios are not supported. For more information about the unsupported scenarios, see Unsupported Transaction Recovery Scenarios . Embedded messaging broker Deprecated The use of an embedded messaging broker in OpenShift containers is deprecated. Support for an embedded broker will be removed in a future release. If a container is configured to use an embedded messaging broker, and if no remote broker is configured, a warning is logged. If the container configuration does not include messaging destinations, set the DISABLE_EMBEDDED_JMS_BROKER environment variable to true to disable the ability to configure an embedded messaging broker. 1.4. Version Compatibility and Support JBoss EAP for OpenShift provides images for OpenJDK 8 and OpenJDK 11. Two variants of each image are available: an S2I builder image and a runtime image. The S2I builder image contains a complete JBoss EAP server with tooling needed during S2I build. The runtime image contains dependencies needed to run JBoss EAP but does not contain a server. The server is installed in the runtime image during a chained build. The following modifications were applied to images in JBoss EAP 7.4 for OpenShift. Default drivers and modules are removed. Templates for MySQL and PostgreSQL are removed. You can provision these capabilities with a custom layer. The Hawkular agent is not active in these images. If configured, it is ignored. The datasource, ExampleDS , is no longer added by default at container startup. If you need the default datasource, use the environment variable ENABLE_GENERATE_DEFAULT_DATASOURCE with a value of true ( ENABLE_GENERATE_DEFAULT_DATASOURCE=true ) to include it. Note The following discovery mechanism protocols were deprecated and are replaced by other protocols: The openshift.DNS_PING protocol was deprecated and is replaced with the dns.DNS_PING protocol. If you referenced the openshift.DNS_PING protocol in a customized standalone-openshift.xml file, replace the protocol with the dns.DNS_PING protocol. The openshift.KUBE_PING discovery mechanism protocol was deprecated and is replaced with the kubernetes.KUBE_PING protocol. Supported architectures for OpenJDK images OpenJDK images support several architectures. This information is summarized in the following table: OpenJDK images and architectures JDK (OS) Architecture supported Red Hat Ecosystem Catalog OpenJDK8 (RHEL 7) x86_64 Builder image and Runtime image OpenJDK11 (RHEL 8) x86_64, IBM Z, and IBM Power Systems Builder image and Runtime image JBoss EAP for OpenShift is updated frequently. Therefore, it is important to understand which versions of the images are compatible with which versions of OpenShift. Additional resources OpenShift and Atomic Platform Tested Integrations Capability Trimming in JBoss EAP for OpenShift 1.4.1. OpenShift 4.x Support Changes in OpenShift 4.1 affect access to Jolokia, and the Open Java Console is no longer available in the OpenShift 4.x web console. In releases of OpenShift, certain kube-apiserver proxied requests were authenticated and passed through to the cluster. This behavior is now considered insecure, and so, accessing Jolokia in this manner is no longer supported. Due to changes in codebase for the OpenShift console, the link to the Open Java Console is no longer available. 1.4.2. IBM Z Support The s390x variant of libartemis-native is not included in the image. Thus, any settings related to AIO will not be taken into account. journal-type : Setting the journal-type to ASYNCIO has no effect. The value of this attribute defaults to NIO at runtime. journal-max-io : This attribute has no effect. journal-store-enable-async-io : This attribute has no effect. 1.4.3. Upgrades from JBoss EAP 7.1 to JBoss EAP 7.4 on OpenShift The file standalone-openshift.xml installed with JBoss EAP 7.1 on OpenShift is not compatible with JBoss EAP 7.4 and later. You must modify a standalone-openshift.xml file installed with JBoss EAP 7.1 before you use it to start a JBoss EAP 7.4 or later container for OpenShift. Additional resources Updates to standalone-openshift.xml when upgrading JBoss EAP 7.1 to JBoss EAP 7.4 on OpenShift 1.5. Deployment options You can deploy the JBoss EAP Java applications on OpenShift using one of the following options: A JBoss EAP for OpenShift template. The EAP operator, a JBoss EAP-specific controller that extends the OpenShift API to create, configure, and manage instances of complex stateful applications on behalf of an OpenShift user. Note The EAP operator is supported only on OpenShift 4 and later versions. Additional resources For more information about JBoss EAP for OpenShift templates, see jboss-eap-openshift-templates on Git Hub . For more information about the EAP operator, see EAP Operator for Automating Application Deployment on OpenShift .

Commands: