IBM Websphere Cluster session sharing problem solving method

Encounter an application deployment environment such as:

Two HTTP servers (IHS) are responsible for forwarding packets, where F5 is in sticky mode, that is, a user's packet within the session cycle must be forwarded to one of the IHS,

However, the server selection between IHS to Web server is distributed randomly , which causes the request session to not be persisted, because the session is required for the management class system deployment.

There are two workarounds for WebSphere:

1. All WebSphere Server session broadcasts, that is, when a machine session notconsistent, notifies all other servers.

2. Modify the configuration in IHS, and communication between IHS and server also uses sticky sessions.

Due to the current number of servers and user volume is not suitable for the use of Method 1, the cost of broadcasting mode is higher, all adopt Method 2, the following specific changes:

1. Prerequisites:

The IHS plug-in is configured so that the WebSphere Management node can manage two IHS (generate plug-in, propagate plug-ins) and restart IHS.

The 1.1 IHS boot must use the 80 port in the Root,linux for only the root process, and the ihs,nodeagent that the WebSphere Management node can manage the root process must also be started with root.

1.2 In the Management node VI%websphere_home%/profiles/dmgr1/config/cells/plugin-cfg.xml

Modify the Servercluster property ignoreaffinityrequests= "False" so that the IHS will bind the machine when the request is distributed.

The implementation of this principle relies on the generation of a cookie named Jessiionid, similar to the value of 00002eiffjm-ql2zityhvfjjmo5:187rufomo

Where the number after the semicolon can represent which server (that is, which JVM process) is specific,

1.3 Enter two IHS servers respectively, vi%ihs_home%/plugins/config/server name/plugin-cfg.xml

Also modify the properties of Servercluster ignoreaffinityrequests= "false"

1.4 into the WebSphere Management console, click Environment, update Global Web server plug-in configuration, OK .

1.5 Restart the IHS service, repeat refresh, authentication is not the request is forwarded to a server.

Note: In the " build plug- in" step,ignoreaffinityrequests will be reset to true again and need to be changed again.

1.6 If you want to change the cookie name used by the session, in the WebSphere Administration console, enter enterprise applications, click Apply to change cookie name, session management, enable cookies,

Change the cookie name, change the cookie domain and cookie path as needed, and then go back to " Session management " to check "overwrite Session management".

IBM Websphere Cluster session sharing problem solving method