This section describes the session management functionality.

The session management is a functionality used for associating the requests and Web clients. This functionality enables you to perform operations in which the same information is inherited from the Web clients across multiple Web pages.

The following table describes the organization of this section.

Table 2-27 Organization of this section (Session management functionality)

Category	Title	Reference
Description	Objects managing the session information	2.7.1
	Session ID format	2.7.2
	Session management method	2.7.3
	Deleting invalid session IDs maintained by the Web client	2.7.4
	Setting the upper limit for the number of HttpSession objects	2.7.5
	Adding a server ID to the session ID and Cookie	2.7.6
Implementation	Definition in cosminexus.xml	2.7.7
Settings	Execution environment settings	2.7.8
Notes	Precautions related to session management	2.7.9

Note:

There is no description of Operations for this functionality.

The session management functionality is also used in the following cases:

• Identification of clients when using the load balancing functionality by clustering
• Identification of clients who have already logged on to the security management functionality

The Servlet specifications clearly describe the method of using Cookies and the method of using URL rewrite as the session management methods. Sessions are managed using these methods even in the Web container of Application Server. However, in the Servlet specifications, there are some parts for which the management method is not specifically described. Therefore, this subsection describes how the session management methods that are not described in the Servlet specifications are managed on Application Server.

This subsection also describes the following three types of session management functionality that are unique to Application Server:

• Deleting invalid session IDs maintained by the Web client
• Setting the upper limit for HTTPSession objects
• Adding server ID to the session ID and Cookie
  

  Hint

  Deleting invalid session IDs maintained by the Web client, setting the upper limit for the HttpSession objects, and adding server ID to the session ID functionality are the prerequisites when using the session failover functionality of Application Server. For the session failover functionality, see 5. Inheriting Session Information Between J2EE Servers in the uCosminexus Application Server Expansion Guide.

Organization of this section

2.7.1 Objects managing the session information

2.7.2 Session ID format

2.7.3 Session management method

2.7.4 Deleting invalid session IDs maintained by the Web client

2.7.5 Setting the upper limit for the number of HttpSession objects

2.7.6 Adding a server ID to the session ID and Cookie

2.7.7 Definition in cosminexus.xml

2.7.8 Execution environment settings

2.7.9 Precautions related to session management