cancel
Showing results for 
Search instead for 
Did you mean: 

Web Dispatcher configured but not working

Former Member
0 Kudos

Hi,

We wish to configure SAP Web Dispatcher as a reverse proxy. For this we've installed using sapinst SAP Web Dispatcher Version 7.00.11, multithreaded, ASCII, 64 BIT Patch Level 140 which was manally updated to SAP Web Dispatcher Version 7.10.1, multithreaded, ASCII, 64 BIT Patch Level 152.

The SAP Web Dispatcher server is in DMZ whereas the Enterprise Portal servers are in the intranet.

The updated SAP Web Dispatcher is available in /sapmnt/<SID>/exe and not in a seperate directory (/usr/sap/<SID>/sapwebdisp) as per SAP note 908097. The SAP Web Dispatcher has been installed on a standalone machine with instance number 00.

I've configured the Sap Web dispatcher with the -bootstrap option. The -checkconfig option completes with 0 warning 0 errors.

The TCP ports between SAP Web Dispatcher and Enterprise Portal servers are opened in the firewall. Also, required ports 22 & 8100 are opened from my computer to the SAP Web Dispatcher Server.

Yet when I try to connect to the administrator interface with the URL http://<Web_Disp_IP>:8100/sap/wdisp/admin/default.html, I receive the following text on the browser:

Network Error (tcp_error)

A communication error occurred: "Operation timed out"

The Web Server may be down, too busy, or experiencing other problems preventing it from responding to requests. You may wish to try again at a later time.

Similar message is received even if the SAP Web Dispatcher is installed in a seperate directory.

Has anyone come across a similar issue?

Thanks.

Regards.

-


SAP Web Dispatcher Profile generated by bootstrap

  1. Profile generated by sapwebdisp bootstrap

  1. unique instance number

SAPSYSTEM = 00

  1. add default directory settings

DIR_EXECUTABLE = .

DIR_INSTANCE = .

  1. Accessibility of Message Servers

rdisp/mshost = <EP_CI_IP_address>

ms/http_port = 8104

  1. SAP Web Dispatcher Parameter

wdisp/auto_refresh = 25

wdisp/max_servers = 100

wdisp/shm_attach_mode = 6

  1. configuration for default scenario (medium size)

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

#maximum number of concurrent connections to one server

wdisp/HTTP/max_pooled_con = 500

wdisp/HTTPS/max_pooled_con = 500

  1. SAP Web Dispatcher Ports

icm/server_port_0 = PROT=HTTP,PORT=8100

icm/server_port_1 =

  1. SAP Web Dispatcher Web Administration

icm/HTTP/admin_0 = PREFIX=/sap/wdisp/admin,DOCROOT=./admin,AUTHFILE=icmauth.txt,PORT=8100

-


WebDisp:wdpadm 16> sapwebdisp pf=sapwebdisp.pfl -checkconfig

Checking SAP Web Dispatcher Configuration

=========================================

maximum number of sockets supported on this host: 8192

Server info will be retrieved from host: <EP_CI_IP_address>:8104 with protocol: http

Checking connection to message server...OK

Retrieving server info from message server...OK

Message Server instance list:

----


--
+

+
--


+

instance name

hostname

HTTP port

HTTPS port

----


--
+

+
--


+

J2EE37031000

sappqxx03

50300

50301

J2EE53924900

sappqxx05

50500

50501

----


--
+

+
--


+

Checking ABAP servers with URL "/sap/public/icman/ping":

no server group "!DIAG" defined

Checking J2EE servers with URL "/index.html":

Checking J2EE server sappqxx03:50300...OK

Checking J2EE server sappqxx05:50500...OK

Web Dispatcher configuration for J2EE only system: No server group !DIAG defined

On double stack systems, configure Web Dispatcher to accessMessage Server of SAP Web AS ABAP

Check ended with 0 errors, 0 warnings

-


Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Bypassed the WDP URL in internet browser

Former Member
0 Kudos

Please refer this [thread|; I posted for this issue as I was having trouble formatting the message when I posted it.

Thanks.

Edited by: SAP Portal Project- e-Ras Laffan on Jun 3, 2009 7:31 AM

Former Member
0 Kudos

Hi,

We wish to configure SAP Web Dispatcher (WDP) as a reverse proxy. For this we've installed using sapinst SAP Web Dispatcher Version 7.00.11, multithreaded, ASCII, 64 BIT Patch Level 140 which was manally updated to Version 7.10.1, multithreaded, ASCII, 64 BIT Patch Level 152.

The SAP WDP server is in DMZ whereas the Enterprise Portal servers are in the intranet.

The updated SAP WDP is available in /sapmnt/<SID>/exe and not in a seperate directory (/usr/sap/<SID>/sapwebdisp) as per SAP note 908097. The SAP WDP has been installed on a standalone machine with instance number 00.

I've configured the Sap WDP with the -bootstrap option. The -checkconfig option completes with 0 warning 0 errors.

The TCP ports between SAP WDP and Enterprise Portal 7.0 SP14 servers are opened in the firewall confirmed as per note 552286. Also, required ports 22 & 8100 are opened from my computer to the SAP WDP Server.

Yet when I try to connect to the administrator interface with the URL http://<Web_Disp_IP>:8100/sap/wdisp/admin/default.html, I receive the following text on the browser:

Network Error (tcp_error)

A communication error occurred: "Operation timed out"

The Web Server may be down, too busy, or experiencing other problems preventing it from responding to requests. You may wish to try again at a later time.

Similar message is received even if the SAP WDP is installed in a seperate directory.

Has anyone come across a similar issue?

Thanks.

Regards.

SAP Web Dispatcher Profile generated by bootstrap

SAPSYSTEM = 00

DIR_EXECUTABLE = .

DIR_INSTANCE = .

rdisp/mshost = <EP_CI_IP_address>

ms/http_port = 8104

wdisp/auto_refresh = 25

wdisp/max_servers = 100

wdisp/shm_attach_mode = 6

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

wdisp/HTTP/max_pooled_con = 500

wdisp/HTTPS/max_pooled_con = 500

icm/server_port_0 = PROT=HTTP,PORT=8100

icm/server_port_1 =

icm/HTTP/admin_0 = PREFIX=/sap/wdisp/admin,DOCROOT=./admin,AUTHFILE=icmauth.txt,PORT=8100

Brief output of checkconfig

Maximum number of sockets supported on this host 8192

Server info will be retrieved from host EPHostIPAddres 8104 protocol http

Checking J2EE server sappqxx03:50300...OK

Checking J2EE server sappqxx05:50500...OK

Web Dispatcher configuration for J2EE only system: No server group DIAG defined

Check ended with 0 errors, 0 warnings

Former Member
0 Kudos

Hi,

Could you, please, reformat your message ?

To be honest, it hurts so much my eyes that I did not read it...

Regards,

Olivier