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

Configure write contents

In session management, we 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 updated through setAttribute method and removeAttribute method calls or we can write all session data properties. This flexibility allows for fewer code changes for the JSP writer when the application will be operating in a clustered environment. The following options are available in Session Management for tuning what is written back:

• Write changed (the default) - Write only session data properties updated through setAttribute method and removeAttribute method calls.
• Write all - Write all session data properties.

The Write all setting might benefit servlet and JSP writers who change Java objects' states that reside as attributes in HttpSession and do not call HttpSession.setAttribute method.

However, the use of Write all could result in more data being written back than is necessary. If this situation applies to you, consider combining the use of Write all with Time-based write to boost performance overall. As always, be sure to evaluate the advantages and disadvantages for the installation.

With either Write Contents setting, when a session is first created, complete session information is written, including all of the objects bound to the session.

Single-row or multi-row schemas. When using database session persistence, in subsequent session requests, what is written to the database depends on whether a single-row or multi-row schema has been set for the session database, as shown in the following table.

Write Contents setting	Behavior with single-row schema	Behavior with multirow schema
Write changed	If any session attribute is updated, all objects bound to the session are written.	Only the session data modified through setAttribute method or removeAttribute method calls is written.
Write all	All bound session attributes are written.	All session attributes that currently reside in the cache are written. If the session has never left the cache, all session attributes are written.

1. Go to the appropriate level of Session Management.

2. Click Distributed environment settings

3. Click Custom tuning parameters.

4. Click Custom settings.

5. Select the appropriate write contents setting.

6. Click OK.

Reference:

Session management tuning

+

Search Tips   |   Advanced Search