If you use the database session failover functionality, the global session information is stored in records of the session information storage table created in a database. When the global session information is stored, one record is assigned to each HTTP session.

On the other hand, if you use the EADs session failover functionality, the global session information is stored in a session information cache on the EADs server.

The information described in the following table is included in the global session information.

Table 5-2 Information included in the global session information

No.	Replication target	Explanation
1	Session ID	A session ID that manages the global session information.
2	HTTP session attribute information	Information that converts the objects of an attribute name and attribute value into serialized byte arrays for the attributes registered in an HTTP session and all the associated attributes.
3	Creation time of an HTTP session	The time of creating an HTTP session. When inheriting a global session, the creation time of an HTTP session before inheritance is used as is.
4	Expiration date of an HTTP session	An expiration date set in an HTTP session.
5	Last access time	The time when requests using an HTTP session are sent for the last time.
6	Identifier of J2EE server which owns HTTP session	A server ID of the J2EE server that creates or inherites an HTTP session.

Reference note

• Database tables used in the database session failover functionality include an application information table that stores the setting information of Web applications, a session information storage table that stores the global session information, and a blank record information table that manages unused records in the session information storage table.
• The cache of an EADs server used in an EADs session failover includes a session information cache that stores the global session information and an application information cache that stores the setting information of Web applications.