Configuring session management by level
When you configure session management at the web container
level, all applications and the respective web modules in the web
container normally inherit that configuration, setting up a basic
default configuration for the applications and web modules below it.
However, you can set up different configurations individually for
specific applications and web modules that vary from the web container
default. These different configurations override the default for these
applications and web modules only.
Configuring session tracking for Wireless Application Protocol (WAP) devices
Applications that run in a web container use sessions to keep
track of individual users. Because most Wireless Application Protocol (WAP)
devices do not support cookies, you can configure WAP devices to use URL rewriting
to track sessions.
Configuring write contents
In session management, you can configure which session data is
written to the database or to another WebSphere® instance, depending on whether
you are using database persistent sessions or memory to memory replication.
You can either write only session data properties that have been updated
through setAttribute method and removeAttribute method calls or you can write
all session data properties.
Configuring write frequency
In the session management facility, you can configure the
frequency for writing session data to the database or to a WebSphere instance, depending on whether
you use database distributed sessions or memory-to-memory replication.
You can write session data using the end of service servlet, manual
update or time based update options.
Last updated: April 18, 2014 05:01 AM CDT http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-iseries&topic=container_httpses_goal_administering_tasks File name: container_httpses_goal_administering_tasks.html