Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Webdispatcher 7.42sp33

We are setting up a proof of concept and wanted to used WebDispatcher. I installed on SUSE WD 7.42 and patch 33.  WD is running fine and I can access from the lan both Admin and MMC.

Initially we want to access one system but set WD up that will allow access to multiple.  We are fine using a single port, so expect to use host as the filter.  so for example host1 and host2 filtering on host1.mydomain.com host2.mydomain.com.

we have setup the

wdisp/system_0 = SID=ONG, MSHOST=host1, MSPORT=8101,

                          SRCSRV=host1.mydomain.com:*

and indeed in webadm we can see ONG details, so I suspect this connection is working fine.

The Webdispatcher ports are setup as follows

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

# SAP Web Dispatcher Ports

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

icm/server_port_2 = PROT=HTTP,HOST=xxxwd1,PORT=8100

icm/server_port_0 = PROT=HTTP,PORT=8888

icm/server_port_1 = PROT=HTTP,HOST=localhost,PORT=81$$

icm/HTTP/admin_0 = PREFIX=/sap/admin,DOCROOT=$(DIR_DATA)$(DIR_SEP)icmandir,AUTHFILE=$(icm/authfile),PORT=81$$

webdispatcher is WD1 on host xxxwd1 (again this is just a proof of concept)

I have also tried

So I expected that everything coming in on host1.mydomain.com:8888 to go to host1.

It isn't and not only that I can't see WD1 ever getting any calls apart from my web access on port 8100.

this SUSE system has the firewall turned off.

port 8888 is forwarded to WD1, for testing I forwarded port 8888 to host1, to make sure our network wasn't the problem, and when I do that I can get to NetWeaver on host1.

Any suggestions on what I am doing wrong or how I can better test it to see traffic on 8888 going through WD1

Tags:
Former Member
Not what you were looking for? View more on this topic or Ask a question