cktechnical
Friday, January 28, 2005
 
IBM WebSphere Session Management
We have multiple WAR projects that we want to have share a single login. That means that we must share the session object throughout all of our web applications. Ibm websphere allows us to do this by enabling a "Shared session context" on the overview tab of the Application Deployment Descriptor in Ibm Webpshere Studio. We must include all of our WAR projects under this main Application but then we will be able to share our session data between our applications.

IBM WebSphere Session Management: "Shared Session Context

Before leaving the session management options, there is one additional option that can be configured in the Application Server Toolkit (ASTK), WebSphere Studio, or the Application Assembly Tool (AAT). This is a J2EE extension that allows for the session object to be shared across the multiple Servlet contexts inside a single enterprise application. While this is a useful option when migrating pre-J2EE applications (Servlet 2.1) to J2EE compliance, we recommend that this be avoided if at all possible. Sharing session in this fashion tends to lead to large session objects that in turn are usually detrimental to application performance. This option is enabled in the ASTK or Studio by selecting the check box indicated in Figure 22-6.

Figure 22.6Figure 22-6 Session sharing option in ASTK.
Distributed Sessions

As previously noted, distributed sessions provide for failover in case of application server outage, allowing an end user to continue using a web site without any loss of an application state that could require a re-login or navigation through previously viewed pages. While local sessions only provide for a single copy of the session object, distributed sessions provide at least one copy of the session object in addition to the local copy that is cached in the application server JVM. It's worth mentioning that aside from ensuring that the information placed into the HTTP session is serializable, there's no impact to application development when choosing to use this option."
Comments: Post a Comment

<< Home

Powered by Blogger