29.01.2013 Views

WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Local sessions (non-persistent)<br />

If the session data is stored in the application server memory only, the session<br />

data is not available to any other servers. Although this option is the fastest and<br />

the simplest to set up, an application server failure ends the session, because<br />

the session data is lost.<br />

The following settings can help you manage the local session storage:<br />

► Maximum in-memory session count<br />

This setting enables you to define a limit to the number of sessions in<br />

memory. This prevents the sessions from acquiring too much of the JVM heap<br />

and causing out-of-memory errors.<br />

► Allow overflow<br />

This setting permits an unlimited number of sessions. If you choose this<br />

option, monitor the session cache size closely.<br />

Note: Session overflow is enabled by default in <strong>WebSphere</strong> <strong>Application</strong><br />

<strong>Server</strong> <strong>V7.0</strong><br />

► Session time-out<br />

This setting determines when sessions can be removed from cache.<br />

Database persistent sessions<br />

You can store session data in an external database. The administrator must<br />

create the database and configure the session database in <strong>WebSphere</strong> through<br />

a data source.<br />

The Use multi-row schema setting gives you the option to use multi-row sessions<br />

to support large session objects. With multi-row support, the <strong>WebSphere</strong> session<br />

manager breaks the session data across multiple rows if the size of the session<br />

object exceeds the size for a row. This also provides a more efficient mechanism<br />

for storing and retrieving session contents when session attributes are large and<br />

few changes are required to the session attributes.<br />

Memory-to-memory replicated persistent sessions<br />

Memory-to-memory replication copies session data across application servers in<br />

a cluster, storing the data in the memory of an application server and providing<br />

session persistence. Using memory-to-memory replication eliminates the effort<br />

of maintaining a production database and eliminates the single point of failure<br />

that can occur with a database. Test to determine which persistence mechanism<br />

is the best one in your environment.<br />

264 <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> <strong>V7.0</strong>: <strong>Concepts</strong>, Planning, and Design

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!