The EAP7 OpenShift Test Plan does not currently include discussion on the testing of EJB client interaction with a deployment on EAP in OpenShift. This is a key ingredient of providing client access to J2EE deployments on EAP in OpenShift.

This issue aims to address that gap in testing of EJB deployments on EAP in OpenShift by updating the test plan to describe the proposed testing, as well as how to carry out test development and to integrate the tests into the existing tests runs for EAP (more specifically, for EAP 8).

According to the  EAP7 Planning Project OpenShift component, there are no stated restrictions involving EJB client access to deployments deployed onto EAP in OpenShift, therefore it is assumed that all EJB client to EAP deployment scenarios supported on non-cloud (bare-metal) environments are intended to be supported on OpenShift.

This includes the following scenarios:

• internal client to internal standalone server (or cluster of servers)
• internal server-client to internal standalone server (or cluster of servers)
• external client to internal standalone server (or cluster of servers)

   where each scenario is supported across the following protocols:

• remote, remote+http
• http

The EJB client functionality which needs to be tested varies with the protocol used. This is particularly true when considering clustered scenarios.

In such a case, when using the EJB client with the "remote" or "remote+http" protocol, the EJB client library implements load balancing and fail-over on behalf of the client, and so has a significant feature set to be tested. On the other hand, when using the EJB client with the "http" protocol in a clustered scenario, a load balancer must be present between the client and the server and responsibility for load balancing and fail-over is delegated to the load balancer.