Forum Discussion
giltjr
Jul 23, 2012Nimbostratus
Are you actually using the F5 to load balance directly to WebSphere? Or is the F5 frontend'ing IBM's HTTP server?
The JSESSIONID for WebSphere has multiple parts. The first part is a unique session id for that user/session. Then there can be 1 or more additional parts that have a unique ID for each WebSphere Server. The additional parts are separated by a colon.
Because of how our system is setup we use a combination of the JSESSIONID and then a pool name to create a universal persistence record.
We have multiple applications with separate pools that all share the same same session id. So we break out the session ID and append it with the pool name for that specific application.