+

Search Tips   |   Advanced Search

Configure session management by level

When we 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 included web modules. 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 we overwrite the default session management settings at the application level, all of its web modules now 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 we change the target mapping after configuring session management, we must return to the session management configuration page in the administrative 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.


Tasks

  1. Open the administrative console.

  2. Change the configuration for the web container, enterprise application, or web module level. The following substeps explain how to access the configuration panels for each of these levels.

    • Web container level:

    • 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

    • 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

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

  4. If we 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.

  5. Click Apply and Save.


Session timeout

Session manager can set up different configurations individually for specific applications and Web modules that vary from the Web container default. Trace messages during application start up don't provide detailed information where the session management configurations are picked up from. That is, Web container level, applications level or Web modules level.

Trace messages from session management configuration by level were modified to include additional details such as overridden configuration at either application level or Web modules level.

The fix for this APAR is currently targeted for inclusion in WebSphere Application Server fix packs 7.0.0.43, 8.0.0.14, 8.5.5.12 and 9.0.0.4. Refer to the Recommended Updates page for delivery information:


Subtopics

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