Configuring HTTP sessions

  • 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

    Review the Session tracking options to plan your approach to session management.

  • 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 for database session persistence

    You can configure a database to collect session data for database session persistence.

  • Configuring memory-to-memory replication for the peer-to-peer mode (default memory-to-memory replication)

    You 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.

  • Configuring memory-to-memory replication for the client/server mode

    You can use the client/server configuration to attain session affinity using a combination of servers that are configured as client only and server only.

  • 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.

Task topic Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Feb 5, 2014 9:49:51 PM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-mp&topic=container_httpses_goal_administering_tasks
File name: container_httpses_goal_administering_tasks.html