Existing EAP customers use the EJB client library to access EJB-based deployments on EAP and such access needs to be provided whether the EAP deployment is on bare metal or on OpenShift. The EJB client application may be internal or external to the cluster, and may use one of three protocols: remote, remote+http, or http (and their encrypted variants).

This issue specifically focuses on the case where the EJB client application is:

• external to the OpenShift cluster
• the transport protocol is http (and its encrypted variants)

This implies that client access to the OpenShift cluster will be via a route or ingress controller configured for the EAP deployment in some way (either manually or via an operator). This is a consequence of the fact that in the case of the http protocol, the EJB client application delegates load balancing and fail-over to a load balancer.

The scope of this issue is to make sure that an EJB client application external to an OpenShift cluster can make use of all the features of the EJB client (as provided on bare metal) to access an operator-controlled Wildfly-based deployment on OpenShift using the http protocol.