Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer web applications
Configure HTTP sessions
- Configure 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.
- Configure session tracking
- Configure 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.
- Configure for database session persistence
We can configure a database to collect session data for database session persistence.
- Configure memory-to-memory replication for the peer-to-peer mode (default memory-to-memory replication)
We can use the peer-to-peer configuration to attain session affinity using a combination of servers that are configured as both client and server. The peer-to-peer configuration contains a single replica by default.
- Configure memory-to-memory replication for the client/server mode
We can use the client/server configuration to attain session affinity using a combination of servers that are configured as client only and server only.
- Configure 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. We 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.
- Configure 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. We can write session data using the end of service servlet, manual update or time based update options.