WAS v8.5 > Administer applications and their environment > Administer web applications > Configure HTTP sessions

Configure session management by level

When configuring 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, we 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. An enterprise application can contain web modules, and so can an OSGi application. At the web container level and at the application level, the process for configuring HTTP sessions is the same whether the web module is part of an enterprise application or an OSGi application. For enterprise applications only, we can also configure HTTP sessions at the web module level.

When overwriting the default session management settings at the application level, all the web modules below the application inherit the new setting unless they too are set to overwrite these settings.

Session management configuration is a post-deployment configuration and is tied to existing targets. If you change the target mapping after you configure session management, you must return to the session management configuration page in the dmgr console or use wsadmin scripting and apply the changes. Apply the changes to module targets if session management is configured for a web module. Apply the changes to all targets if session management is configured for an application level.

  1. Open the dmgr console and access the configuration panels for each of these levels...

    • For the web container level:

        Servers | Server Types | WebSphere application servers | server_name | Container Settings | Container Settings | Web container | Additional Properties | Session management

    • For the application level:

      If the application is an enterprise application:

        Applications | Application Types | WebSphere enterprise applications | application_name | Web Module Properties | Session management

      If the application is an OSGi application:

        Applications | Application Types | Business-level applications | application_name | eba_asset_name | Additional Properties | Session management

    • For the web module level, if the application is an enterprise application:

        Applications | Application Types | WebSphere enterprise applications | application_name | Modules | Manage Modules | module_name | Additional Properties | Session Management

  2. Manage sessions by configuring session tracking, session timeouts and serializing access.

  3. If you are working at the web module or application level and want these settings to override the inherited Session Management settings, under General Properties select Override session management.

  4. Click Apply and Save.


Subtopics

  1. Session management settings
  2. Session recovery support


Related

Configure session tracking
Configure for database session persistence
Session management custom properties


+

Search Tips   |   Advanced Search