Session configuration is done by directly specifying values for WAM properties. There are properties for configuring how the session key is stored in the browser and for setting the inactivity timeout period of the session. (You will find details in 4.3.6 WAM Session Properties.)
By default, each WAM maintains its own session state independent of other WAMs; however, you can chain multiple WAM sessions as a single session. Chaining is useful in situations where multiple WAMs comprise a single Web application.
WAMs allow you to specify the behavior on session expiry or when a session is invalid. You can provide an event handler for the event that is signaled when a session is invalid or expired. The code in the event handler might show a custom error page, or re-direct to a logon page, or provide some other functionality.