Forum Discussion
Chris_Miller
Feb 21, 2011Altostratus
Aaron - the flow is like this: Client -> VIP -> WebSEAL Pool member -> VIP -> WebLogic Pool Member
At the WebSEAL VIP, source address persistence is just fine. Since my WebSEAL Pool Members will be the devices sending traffic to the WebLogic pool, connections are essentially proxied so using an address-type persistence kills the ability to load balance requests adequately.
From a cookie insertion perspective, I've enabled cookie persistence at the WebLogic VIP. Unfortunately, WebSEAL rewrites the name of the cookie per the document above. I'm exploring whether our WebSEAL team can make changes. If worst came to worst, I can come up with something using an iRule but didn't understand what options were available with the out-of-box cookie profile as I've really only ever used iRules.