webdispatcher load balancing recommendations

[Former Member]

I currently have a webdispatcher in front of a CI and 2 App servers running NWCE JAVA only using end-to-end SSL.  Currently the load balancing doesn't seem to be functioning correctly as all the load is being pushed to just one App server and the other is sitting idle.  weighted round robing is currently set as the load balancing strategy, which is the prefered setting for E2E SSL.  Below is a copy of my instance profile.  Can any one provide any feed back on what setting to change or modify to help?   Also, is there a way to point requests from certain IPs to just one app server and all other requests to the other?  Thanks in advance!

SAPSYSTEMNAME = CWD

SAPGLOBALHOST = xxxx

SAPSYSTEM = 00

INSTANCE_NAME = W00

DIR_CT_RUN = $(DIR_EXE_ROOT)\$(OS_UNICODE)\NTAMD64

DIR_EXECUTABLE = $(DIR_CT_RUN)

DIR_PROFILE = $(DIR_INSTALL)\profile

_PF = $(DIR_PROFILE)\CWD_W00_xxxxx

SETENV_00 = PATH=$(DIR_EXECUTABLE);%(PATH)

#-----------------------------------------------------------------------

# Accesssability of Message Server

#-----------------------------------------------------------------------

rdisp/mshost = xxxxx

ms/http_port = 8101

ms/https_port = 8080

#ms/https_port = 443

#-----------------------------------------------------------------------

# Configuration for medium scenario

#-----------------------------------------------------------------------

icm/max_conn = 500

icm/max_sockets = 1024

icm/req_queue_len = 500

icm/min_threads = 10

icm/max_threads = 50

mpi/total_size_MB = 80

#-----------------------------------------------------------------------

# SAP Web Dispatcher Ports

#-----------------------------------------------------------------------

icm/server_port_0 = PROT=HTTP,PORT=81$$

icm/server_port_1 = PROT=HTTP,PORT=80,TIMEOUT=3600,PROCTIMEOUT=3600

icm/server_port_2 = PROT=ROUTER,PORT=443,TIMEOUT=60,PROCTIMEOUT=600

#-----------------------------------------------------------------------

# Start webdispatcher

#-----------------------------------------------------------------------

_WD = $(DIR_EXECUTABLE)\sapwebdisp$(FT_EXE)

Start_Program_00 = local $(_WD) pf=$(_PF)

icm/HTTP/redirect_0 = PREFIX=/, FROM=*, FROMPROT=http, PROT=https, HOST=vxxxxx

icm/HTTP/redirect_1 = PREFIX=/, FOR=xxxxx, TO=xxxxx

icm/HTTP/redirect_2 = PREFIX=/index.html, FOR=xxxxx, TO=xxxxx

is/HTTP/show_server_header = false

is/HTTP/show_detailed_errors = FALSE

icm/HTTP/error_templ_path = E:\usr\sap\CWD\W00\data\icmerror

wdisp/HTTPS/dest_logon_group = !J2EES

wdisp/load_balancing_strategy = weighted_round_robin

wdisp/enable_j2ee_groups = TRUE

wdisp/force_dest = JAVA

ssl/ssl_lib = $(DIR_EXECUTABLE)$(DIR_SEP)$(FT_DLL_PREFIX)sapcrypto$(FT_DLL)

sec/libsapsecu = $(ssl/ssl_lib)

ssf/ssfapi_lib = $(ssl/ssl_lib)

[Benny]

First thing you should try is to call the message server and see what it brings back:

http://<servername>:8101/msgserver/text/logon?version=1.2

The answer to this should include a list of all servers in the cluster. If your second server is not included you know the problem already.

Details.

If both servers are listed, start your web dispatcher with a standard config and see if the problem still occurs.

Regards,

Benny

[hemanth2]

Hi Jayson,

Hope you are doing good.

The web dispatcher will use the load data from the message server so the first step for checking is the weighting and load in SMLG.

Would you make sure that /public/icf_info is activated in SICF?

This can also happen if the URL prefix table could not be received from the message server.

Please also have a look into note 552286.

Also note that if the application is stateful. The SAP Web dispatcher ensures that with the next request, the user is forwarded to the server that is processing his or her application. To do this, it uses the session cookie with HTTP connections, and the client IP address with end-to-end SSL (see also SAP Web Dispatcher and SSL).

Finally, the most important thing is using the latest web dispatcher kernel patch. We improved the load distribution in the higher patch level, so please do upgrade the kernel patch of web dispatcher to the latest one as per note 908097.

Thank you and have a nice day :).

_____________

Kind Regards,

Hemanth

[Former Member]

Hemanth,

That doesn't help me because my backend is not ABAP.  This is a JAVA only system.