SAP Web Dispatcher in a high availability environment

[Former Member]

Hello, guys

We are working in a CRM 7.0 implementation Project. Our system landscape is the following:

- Two hosts (host1 & host2) on MSCS cluster (Windows 2008) with SQL Server and ASCS in high availability. Additional, this MSCS cluster has a instance of SAP Web Dispatcher.

- In these two host weu2019ve installed a CI & DI instance, outside of high availability scope

- Two additional hosts (host3 & host4) with one dialog instance in every host

We have severe problems with communication between SAP Web Dispatcher and ICM components. Our configuration schema is the next:

- ASCS (MSCS_virtual_hostname):

• ms/server_port_0 = PROT=HTTP,PORT=8141

• SAPLOCALHOSTFULL = <MSCS_virtual_hostname>.<domain>

- IC (host1)

• icm/server_port_0 = PROT=HTTP,PORT=8040,TIMEOUT=90,PROCTIMEOUT=600

• icm/host_name_full = <host1>.<domain>

- ID1 (host2)

• icm/server_port_0 = PROT=HTTP,PORT=8044,TIMEOUT=90,PROCTIMEOUT=600

• icm/host_name_full = <host2>.<domain>

- ID3 (host3)

• icm/server_port_0 = PROT=HTTP,PORT=8045,TIMEOUT=90,PROCTIMEOUT=600

• icm/host_name_full = <host3>.<domain>

- ID4 (host4)

• icm/server_port_0 = PROT=HTTP,PORT=8046,TIMEOUT=90,PROCTIMEOUT=600

• icm/host_name_full = <host4>.<domain>

- SAP Web Dispatcheer (MSCS_virtual_hostname):

• SAPGLOBALHOST = <MSCS_virtual_hostname>

• SAPLOCALHOSTFULL = <MSCS_virtual_hostname>.<domain>

• SAPLOCALHOST = <MSCS_virtual_hostname>

• SAPLOCALHOST = <MSCS_virtual_hostname>

• ms/http_port = 8141

• icm/server_port_0 = PROT=HTTP, PORT=8042,TIMEOUT=30,PROCTIMEOUT=600

• wdisp/add_xforwardedfor_header = TRUE

In SAP Web Dispatcher log weu2019ve found the following error messages:

Fri Jan 28 15:45:22 2011

***LOG Q0I=> NiPConnect2: connect (10061: WSAECONNREFUSED: Connection refused)

*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 6 / sock 130060

(SI_ECONN_REFUSE/10061; I4; ST; 192.168.6.182:8044)

*** ERROR => Connection request to host: , service: 8044 failed (NIECONN_REFUSED)

SAP Web Dispather is trying to connect to connect with dialog instances through , which itu2019s incorrect (ports 8044, 8045 & 8046 are opened in dialog instances, not in virtual instance). I think it should try with real hostnames (host1, host2, host3 & host4).

¡¡Please, help!! Thanks in advance

[Former Member · Accepted solution]

Hi,

Your explanations about your configuration are not very clear.

I don't understand why you use so many different HTTP ports.

It would be so much simpler to use the same http port for the CI and the 3 DI.

Where is the SAP Web dispatcher ? Is it also a cluster ressource ? or is it on host 4 ? (which would not seem logical, think SPOF...)

Try to increase the web dispatcher trace level et see if you can get useful information for it.

Regards,

Olivier

[Former Member]

Hi, Olivier

We solved our problem last Friday. We made incorrect settings in our ICM components. Our final configuration is:

- SAPLOCALHOSTFULL: full qualified domain name of every server (host1, host2, host3 & host4). Each application server has its hostname parameter value.

- HTTPURLLOC: We added one entrie with the following values:

• Client: <Our client>

• Sort Key: 010

• Protocol: HTTP

• Application: *

• Hostname with domain: <SAP_Web_Dispatcher_FQDN>

• Port: <Port_SAP_Web_Dispatcher>

With this configuration, our SAP Web Dispatcher is making a correct balancing between our application servers.

Best regards,

Sergio

[Former Member]

Hello There,

I am exactly having the same problem in my ECC6 env. We have one CI (ABAP) and 4 dialog instance. We have configured webdispatcher in CI and installed Java stack in the Seperate host.

Could you u help to share your webdisp profile and ICM parameter profile details plz.

Regards

Karthi

[Former Member]

Hello, Karthi,

Our Web Dispatcher profile looks as following:

#----

---

1. Instance specific parameters

#----

---

1. Maybe some of these parameters are needless

SAPSYSTEMNAME = <CRM SID>

INSTANCE_NAME = <WD SID>

SAPSYSTEM = <WD System number>

SAPGLOBALHOST = <virtual hostname of WD>

SAPLOCALHOSTFULL = <FQDN of virtual hostname of WD>

SAPLOCALHOST = <virtual hostname of WD>

#----

---

1. Directorios

#----

---

DIR_INSTANCE = R:\usr\sap\wd

DIR_INSTALL = R:\usr\sap\wd

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

DIR_EXECUTABLE = R:\usr\sap\wd

DIR_PROFILE = R:\usr\sap\wd

DIR_HOME = R:\usr\sap\wd

DIR_ICMAN_ROOT = $(DIR_INSTANCE)\icmanroot

R:\usr\sap\wd\global\security\data

#----

---

1. Accesibilidad al Message Server

#----

---

rdisp/mshost = <virtual hostname of CRM Message Server>

ms/http_port = <HTTP port of CRM Message Server>

#----

---

1. HTTP Settings

#----

---

1. Puerto estandar de acceso HTTP

icm/server_port_0 = PROT=HTTP, PORT=8042,TIMEOUT=30,PROCTIMEOUT=600

1. These parameters defines load balancing weights

#wdisp/server_00 = NAME=<hostname_SID_SYSNR>, LB=4, ACTIVE=0

#wdisp/server_01 = NAME=<hostname_SID_SYSNR>, LB=10, ACTIVE=1

#wdisp/server_02 = NAME=<hostname_SID_SYSNR>, LB=20, ACTIVE=1

#wdisp/server_03 = NAME=<hostname_SID_SYSNR>, LB=20, ACTIVE=1

1. Puerto de acceso interfaz web de administrador

icm/HTTP/admin_0 = PREFIX=/sap/admin, DOCROOT=$(DIR_ICMAN_ROOT)/admin, AUTHFILE=$(DIR_INSTANCE)\sec\icmauth.txt

1. Activaciu00F3n de la cachu00E9 de SAP Web Dispatcher

icm/HTTP/server_cache_0/http_cache_control = true

icm/HTTP/server_cache_0 = PREFIX=/, CACHEDIR=$(DIR_INSTANCE)\cache

1. Fichero de log de seguridad

icm/security_log = LOGFILE=$(DIR_HOME)\log\security_%y%m%d.log, SWITCHTF=day, MAXSIZEKB=1024, FILEWRAP=off

icm/HTTP/logging_0 = PREFIX=/, LOGFILE=$(DIR_HOME)\log\wd_log_%y%m%d.log, SWITCHTF=day, MAXSIZEKB=1024, FILEWRAP=off

icm/log_level = 1

#----

---

1. Dispatcher Configuration

#----

---

wdisp/add_xforwardedfor_header = FALSE

#----

---

1. Parametrizacion de memoria

#----

---

#######################################################################

1. Datos de sizing de los que se parten #

#######################################################################

#users = 1800 usuarios (900 concurrentes)

#req_per_dialog_step = 6 peticiones HTTP por paso

#thinktime_per_diastep_sec = 10 seg. de "thinktime"

#conn_keepalive_sec = 30 seg. mantener conexiu00F3n abierta con ICM

#icm/max_conn = users * req_per_dialog_step * conn_keepalive_sec / thinktime_per_diastep_sec

icm/max_conn = 16200

1. wdisp/HTTP/max_pooled_con = icm/max_conn

wdisp/HTTP/max_pooled_con = 16200

1. icm/max_sockets = al menos la suma de icm/max_conn y wdisp/HTTP/max_pooled_con

icm/max_sockets = 32400

1. mpi/buffer_size = 64K = 64 * 1024 = 65536

mpi/buffer_size = 65536

1. mpi/total_size_MB = icm/max_conn * mpi/buffer_size (hay que convertir mpi/buffer_size a MB)

mpi/total_size_MB = 1024

1. icm/req_queue_len = icm/max_conn / 2

icm/req_queue_len = 8100

1. icm/min_threads = icm/max_conn / ~50

icm/min_threads = 512

1. icm/max_threads = icm/max_conn / ~20

icm/max_threads = 1024

#----

---

1. Parametrizacion de seguridad

#----

---

1. Evitar el envu00EDo de mensajes tu00E9cnicos al usuario final

is/HTTP/show_detailed_errors = FALSE

#

#icm/HTTP/error_templ_path

And ICM parameters are:

- SAPLOCALHOSTFULL= <FQDN of every application server>

- icm/server_port_0 = PROT=HTTP,PORT=8080,TIMEOUT=90,PROCTIMEOUT=600:

- icm/host_name_full = <FQDN of every application server> ## This parameter is ignored if SAPLOCALHOSTFULL is defined

I hope it helps you.

Best regards,

Sergio Su00E1nchez