Using ActivitySessions with HTTP sessions

This topic describes how a web application that runs in the WebSphere Web container can participate in an ActivitySession context.

If the web application is designed such that several servlet invocations occur as part of the same logical application, then the servlets can use the HttpSession to preserve state across servlet invocations. The ActivitySession context is one state that can be suspended into the HttpSession and resumed on a future invocation of a servlet that accesses the HttpSession.

An ActivitySession is associated automatically with an HttpSession, so can be used to extend access to the ActivitySession over multiple HTTP invocations, over inclusion or forwarding of servlets, and to support EJB activation periods that can be determined by the lifecycle of the web HTTP client. An ActivitySession context stored in an HttpSession can also be used to relate work for the ActivitySession back to a specific web HTTP client.

The Web container manages ActivitySessions based on deployment descriptor attributes associated with servlets in the Web application module. The two usage models are:

A Web application can invoke servlets configured for either usage model.

The following points apply to both usage models:


Related concepts
The ActivitySession service
ActivitySession and transaction contexts
The ActivitySession service application programming interfaces
Related tasks
Setting Web module ActivitySession deployment attributes with the Assembly Toolkit[Version 5.0.2 and later]
Setting ActivitySession deployment attributes for a Web application[5.0 only][Version 5.0.1][Version 5.0.2]



Searchable topic ID:   cas_ohttp
Last updated: Jun 21, 2007 8:07:48 PM CDT    WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/ass/concepts/cas_ohttp.html

Library | Support | Terms of Use | Feedback