cancel
Showing results for 
Search instead for 
Did you mean: 

Cascade web dispatcher

Former Member
0 Kudos

We are using cascade web dispatcher as explained in note 740234. Users

connect to the URL of an F5 device through https, which is a SSL

terminator and connect the 1st web dispatcher in the DMZ through http,

then connect to the 2nd web dispatcher behind the firewall through

http, and then connect to SAP portal through http. We are having

performance issues with web dispatcher during stress test. I am hoping

to improve performance using recommendations in note 953784 (SAP Web

Dispatcher Connection Pooling), which suggests to set

wdisp/HTTP/use_pool_for_new_conn=1, and #the back end keep-alive time

out should be at least 20 seconds longer than the Web Dispatcher's keep-

alive timeout#. I have the following questions:

1.Do you think note 953784 may help in our landscape described above?

If so,

2.Should both web dispatchers have disp/HTTP/use_pool_for_new_conn=1?

3.Should the 2 web dispatchers have the same keep-alive time out value,

or should the 2nd web dispatcher have a higher keep-alive time out

value than the 1st web dispatcher?

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

>1.Do you think note 953784 may help in our landscape described above?

I don't think so because you don' use HTTPS on the web dispatchers.

>2.Should both web dispatchers have disp/HTTP/use_pool_for_new_conn=1?

Just try it but I gues it will not make a big difference. (I may be wrong)

>3.Should the 2 web dispatchers have the same keep-alive time out value,

>or should the 2nd web dispatcher have a higher keep-alive time out

>value than the 1st web dispatcher?

I would use a lightly higher time out for the 2nd web dispatcher.

What load do you use for your stress test ?

How many HTTP requests per second ?

Did you set enough MPI buffers and threads on your web dispatchers ?

Regards,

Olivier

Answers (0)