In this post we take a look at WebLogic session management. We will take a look at Coherence*Web, and see how things have simplified in WebLogic 12.1.2 when compared to WebLogic 12.1.1. We use the Java 7 Flight Recorder to analyze some WebLogic diagnostics. To persist sessions we have the following options. 
- In-memory replication – node that Web applications which have persistent store type set to replicated or replicated_if_clustered will have to be targeted to the cluster or all the nodes of that cluster. If it is targeted to only some nodes in the cluster, the Web application will not be deployed. In-memory replication requires that Web applications be deployed homogeneously on all the nodes in a cluster.
- JDBC-based persistence – WebLogic maintains the HTTP session state using file-based or JDBC-based persistence. Coherence*Web – a remark from the documentation: “
- Coherence*Web is not a replacement for WebLogic Server’s in-memory HTTP state replication services. However, you should consider using Coherence*Web when an application has large HTTP session state objects, when running into memory constraints due to storing HTTP session object data, or if you want to reuse an existing Coherence cluster.” To configure a persitent type set the persistent Read the full 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.
Blog 
Twitter 
LinkedIn 
Mix 
Forum 
Wiki
Technorati Tags: Rene van Wijk,Weblogic session management,WebLogic,WebLogic Community,Oracle,OPN,Jürgen Kress
Developer Community 