SAP AS Java Administration · Load Balancing & Web Dispatcher

The SAP Web Dispatcher keeps a stateful user on the same server process. Why does it use a different stickiness key for plain HTTP than for end-to-end SSL?

Answer locked. Get the free KnowCard app to reveal it — plus spaced-repetition review so it actually sticks.

This is one card from the KnowCard library — thousands more across SAP, Linux, Python and more. In the app you get the answer, AI explanations, and cards that come back right before you would forget them. Free to start on iOS, Android or the web.

More in Load Balancing & Web Dispatcher

SAP recommends server-based load balancing over client-based. What is the concrete operational payoff that drives that recommendation?

In client-based load balancing, how does a client end up talking to a specific application server, and by which two mechanisms is this realized?

Both the message server method and the SAP Web Dispatcher balance HTTP load. What is the fundamental behavioral difference, and what extra role does that let the Web Dispatcher fill?

Do you download or separately purchase the SAP Web Dispatcher, and which system landscapes can it load-balance?

Why is the message-server HTTP-redirect method not SAP's preferred load balancing approach? Name its practical drawbacks.

For a load balancer, why are stateful web applications the hard case rather than stateless ones?

Start learning today

Free to start — download the app or use it in your browser.