About this task
You can use the HTTP session manager with other application
servers that are not running
WebSphere Application Server,
such as
WebSphere Application Server Community Edition. To configure
other application servers to use the data grid, you must splice your
application and incorporate
WebSphere eXtreme Scale Client Java
archive (JAR) files into your application.
What to do next
You can change a majority of the configuration attributes
for the session manager when you instrument your application to use
the session manager. These attributes include variations to the replication
type (synchronous or asynchronous), in-memory session table size,
and so on. Apart from the attributes that can be changed at application
instrumentation time, the only other configuration attributes that
you can change after the application deployment are the attributes
that are related to the
WebSphere eXtreme Scale server
cluster topology and the way that their clients (session managers)
connect to them.
Remote scenario behavior:
If the entire data grid that is hosting the application session data
is unreachable from the web container client, the client instead uses
the base web container of the application server for session management.
The data grid might be unreachable in the following scenarios:
- A network problem between the Web container and the remote container
servers.
- The remote container server processes have been stopped.
The number of session references kept in memory, specified by
sessionTableSize parameter,
is still maintained when the sessions are stored in the base web container.
The least recently used sessions are invalidated from the web container
session cache when the
sessionTableSize value
is exceeded. If the remote data grid becomes available, sessions that
were invalidated from the web container cache can retrieve data from
the remote data grid and load the data into a new session. If the
entire remote data grid is not available and the session is invalidated
from the session cache, the user session data is lost. Because of
this issue, do not shut down the entire production remote data grid
when the system is running under load.