Coherence*Web is a great feature which allows you to store your HTTP
sessions in a Coherence Cluster. Doing this allows your to de-couple the
HTTP sessions from your JVM’s that are running your web apps, (which
can free up JVM memory) and take advantage of the RASP (Reliability,
Availability, Scalability and Performance) capabilities of Coherence for
storage.
With this separation you can also more easily scale and manage and your HTTP session tier as well as utilise the wide array of session management options that Coherence*Web provides.
What I’d like to show you here is how to configure Coherence*Web in WebLogic Server 12.1.2 and deploy a basic web application that utilises this.
For more detailed information on Coherence*Web and the options available, see http://docs.oracle.com/middleware/1212/coherence/COHCW/start.htm#sthref11.
Setup
For
this example, I’m assuming you already have installed WebLogic Server
12.1.2 and created a domain with node manager running.
If you are not familiar with how to do this, then you can use one of my posts here as a starting point or see the product documentation here.
We
are going to create two WebLogic Server Clusters and a Coherence
cluster into which we shall place both WLS clusters. This will ensure
that the manages servers in both WLS clusters are associated with a
common set of Coherence caching services. Read the complete article here.
For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.
