In our current envrionment we have a web dispatcher that points to two
physical servers that are each running two server processes for
Portal. We have noticed that as users enter through the dispatcher
they are bounced back and forth between the two servers and server
processes. How can it be configured so that the dispatcher will redirect
all request to the same server/process after the initial connection is
established. Below you can see from the cookie that the server changes
from Node1 to Node2 and the server process number
changes as well.
1. Opening the home page (/irj/portal/anonymous) gives a response with
set-cookie="saplb_*=(<b>Node1_EQ1_02)26862150</b>; Version=1;
Path=/". One of the iViews (isolation method of URL) on that page is
sending a set-cookie="saplb_*=(<b>Node2_EQ1_02)24821850</b>;
Version=1; Path=/".
2. Clicking the login button (/irj/portal/anonymous/login) causes the
set-cookie="saplb_*=(<b>Node1_EQ1_02)26862151</b>; Version=1; Path=/"
to be set back in the response
of "GET /irj/servlet/prt/portal/prtroot/com.sap.portal.wsrp.coreconsumer.WSRPSessionRelease HTTP/1.1"
3. Submitting the login form causes two set-cookie entries to be
returned: "MYSAPSSO2=AjExMDAgABFwb3J0YWw6UFVSQ0hfVVNFUogAE2Jhc2ljYXV0aGVudGljYXRpb24BAApQVVJDSF9VU0VSAgADMDAwAwADRVExBAAMMjAwNzA1MjExNzA4BQAEAAAACAoAClBVUkNIX1VTRVL%
2FAQQwggEABgkqhkiG9w0BBwKggfIwge8CAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHATGBzzCBzAIBATAiMB0xDDAKBgNVBAMTA0VRMTENMAsGA1UECxMESjJFRQIBADAJBgUrDgMCGgUAoF0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMDcwNTIxMTcwODQyWjAjBgkqhkiG9w0BCQQxFgQUdxJAhLB0SLUDxIqLL%2Fo4SL%
2FYziAwCQYHKoZIzjgEAwQuMCwCFCeEFN7JAoc3XLMLaxaDA27QTINyAhRRhQwqJNa0geu41hlxEbOyE0r34Q%3D%3D;path=/;domain=bungeservices.com;HttpOnly"
and "saplb_*=(<b>Node2_EQ1_02)24821850</b>; Version=1; Path=/" which
is followed by a request for "GET /irj/portal/anonymous/login HTTP/1.1"
which returns a set-cookie="saplb<b>_*=(Node1_EQ1_02)26862151</b>;
Version=1; Path=/".