In this article, I will show how you can implement a common use case that often happens when you migrate a classic Java EE application into a Red Hat OpenShift environment.
Usually a classic Java EE application stores a user’s information, such the profile’s configuration, in the HTTP session. In a typical production scenario, there are several application server instances that build a cluster and are used to implement high availability, failover, and load balancing. To make sure that stateful information is preserved across the application server instances, you must distribute your session as described in the Java EE 7 specification section EE.6.4, “Servlet 3.1 Requirements.”
Continue reading “Externalized HTTP Session in an OpenShift 3.9 Environment”