The Web application Server features session tracking (that is, tracking user requests). Use the session tracing page of manager to configure session tracking. The session tracker merges several related requests from the same user into a single session (that is, a HttpSession object). A session tracker can also enable multiple instances of a Web application server to share a common buffer pool of sessions (that is, a session cluster).
- 1. Enable session tracking and its parts
View the session tracking page. Click the Enable tab. The following fields can be set in the Enable tab.
(1) Enable session: Whether session tracing is enabled, that is, whether the request and response object's related session mode is valid. The default value is yes.
(2) Enable URL rewriting: refers to whether the session trace enables the rewrite URL to get the session identifier. If enabled, session tracking
The program will identify the session identifier that arrives at the URL and, if necessary, rewrite the URL and send the session identifier. The default value is.
(3) Enable cookies: refers to whether session tracking uses cookies to carry session identifiers. If yes, the session tracker will
Identifies the session identifier that is reached as a cookie and uses the cookie as the way to send the session identifier. The default value is yes.
(4) Enable protocol translation rewriting: When a URL requires conversion from HTTP to HTTPS, or from HTTPS to HTTP,
Whether to add the session identifier to the URL. The default value is No.
- 2. Create a Cookie that carries a session identifier
Specifies the setting of a cookie that the session tracker uses to place related individual requests into a logical user session. When a Servlet requests a HttpSession object to represent a user session, the session tracker can use a Cookie to pass a unique session identifier back to the requesting browser. When a servlet makes a subsequent request, the Cookie is allowed to be sent back and forth between the servlet and the session tracker. The session tracker uses it to find an existing HttpSession object for the user Servlet. In other words, the session tracker uses the identifier in the Cookie to determine that the request is related to the user's other requests.
View the session tracking page. Click the Cookie tab. Specifies the name of the Cookie, and the default value is Sesessionid. Optionally, specify the following fields:
(1) The value of the domain field to restrict where the Cookie is sent.
(2) The active time of the session Cookie on the client browser (that is, the "Maximum period" field, in milliseconds). If the field is empty, the Cookie is deleted when the browser is closed.
(3) The value of the Path field to specify the server path to which the Cookie is sent.
(4) Click Yes in the security field to restrict the exchange of cookies that only allow HTTPS sessions.
- 3. Set time and parameters for session tracking activity
View the session tracking page. Click the Interval tab.
(1) Specifies the interval (in milliseconds) that the session tracker checks whether the session is idle and whether the session is invalid.
(2) Specifies the frequency, in milliseconds, that the session tracker will swap sessions to disk because of excessive in-memory sessions.
(3) Specify the number of sessions (maximum number of hosts) that are allowed to remain in memory at one time.
(4) Specifies the time, in milliseconds, that a session will allow to remain idle before the session tracker stops verifying.
Use the Persistence tab to specify whether session data is swapped to disk after the session tracker shuts down and restarts. If the persistence field is set to No, the session tracker deletes the old session Exchange file on each startup. View the session tracking page. Click the Persistence tab. In the Durability field, click Yes. Specifies that session tracker is used to store session data to be persisted. Note: The swap directory must be an empty directory.
- 5. Specifying session Clustering and Protocol conversion settings
The WebSphere Application server can be configured to run as a standalone host, session Cluster Server, session cluster client, protocol translation host, and stand-alone host. Review the Session tracking page and click the Hosts tab.
(1) If the WebSphere Application Server instance is a standalone host, it does not participate in the session cluster. In standalone mode, the WebSphere Application server maintains its own session information, while the session information request to the customer is not responded to, and the session information is not requested from the server. Default value: Yes.
(2) In an environment that uses products such as IBM enetwork Dispatcher to cluster WEB servers, specify the host name and IP address of the WebSphere application Server instance, where the instance is a session cluster server.
(3) If you configure the WebSphere Application Server instance as URL rewriting and protocol translation (in the Enable Session Tracking tab), indicate the host name or IP address of the cluster host. For example, the IBM enetwork Dispatcher host may be.
For the changes to take effect, restart the Web application server after you change the standalone host or Session Cluster Server fields. Changes made to all configurations after these fields are changed are saved in the configuration file until they are restarted.
websphere--Session Tracking
