SAP Web dispatcher and WebAS 6.20 ?

[Former Member]

Hi all,

I'm trying to configure a standalone SAP Web dispatcher (SWD) to access our WebAS (WAS), but I don't understand how to setup the configurations files.

Currently I can reach the SWD admin via: http://swdhost:81/sap/wdisp/admin/default.html

The WebAS (ABAP) service I want to access is at:

http://washost/ris

The SWD pfl file looks like this:

# Profile generated by sapwebdisp bootstrap

# unique instance number
SAPSYSTEM = 1

# Accesssability of Message Servers
rdisp/mshost = swdhost
ms/http_port = 80

# SAP Web Dispatcher Parameter
wdisp/auto_refresh = 120
wdisp/max_servers = 100
wdisp/url_map_location = file://urlprefix.txt

# SAP Web Dispatcher Ports
icm/server_port_0 = PROT=HTTP,PORT=81

# SAP Web Dispatcher Web Administration
icm/HTTP/admin_0 = PREFIX=/sap/wdisp/admin,DOCROOT=./admin 

Urlprefix.txt looks like this:

version 1.0
PREFIX=%2fRIS%2f&CASE=&VHOST=%2a%3a%2a%3b

Now after reading most of the post in the forum and the docs, I still cant understand how I can "say" to SWD to map http://swdhost:81/ris to http://washost/ris .

Thanks in advance for your help.

Best Regards

Erik

[Former Member]

Hi Erik,

It looks like you need to change your SWD pfl file

I'm assuming that washost is the central instance.

Please run Tx RZ11 on washost and lookup the value of ms/http_port

Then change your profile file to:

1. Accesssability of Message

Serversrdisp/mshost = washost

ms/http_port = <the value you just got from RZ11>

Also make sure you activate the following servicers in Tx SICF:

/sap/public/icman

/sap/public/icf_info/*

Best regards,

Alexander

[Former Member]

Hi Alexander,

Thanks, the ms/http_port parameter was not set in my WAShost, now the SWD can see the WAS

now if I try to reach :

http://WAShost:81/sap/public/ping , I get a reply from my WAShost.

but I can't reach http://SWDhost:81/ris or http://SWDhost:81/sap/bc/was/sap/zris

http://WAShost/ris is an alias of http://WAShost/sap/bc/was/sap/zris.

Anyway thanks already.

Cheers

Erik

[Former Member]

Well It works now!

The SDW was not in the same domain as WAS and not resolving the url correctly.

Thanks for all your replies!

next step ... moving the SDW to the DMZ and add SSL

Cheers

Erik

[former_member185954]

Hi,

You have to do the mapping in transaction SICF and create Virtual Host, this part of configuration is on the ICM side.

Check the below link for why Virtual Host is required.

http://help.sap.com/saphelp_erp2004/helpdata/en/a8/a8463c53a0ff02e10000000a114084/frameset.htm

For configuring the Virtual Host check this link

http://help.sap.com/saphelp_erp2004/helpdata/en/85/5c543aa24b511ce10000000a11402f/frameset.htm

This should make things clear.

hope that helps

Regards,

Siddhesh

[Former Member]

Hi,

Thanks for the reply.

I've to say that I'm really lost with that.

Those documents refer to a SAP Web dispatcher AND Web-AS running on the same server.

My problem is that we try to use one server for SWD and one for WAS.

So currently I'm lost in what parameters I need to put in the SWD profile to make it "see" my WAS.

Regards

Erik

[Former Member]

There is a SAP Note 552286 titled "Trouble shooting the web dispatcher" it might address your questions.

It explains what ports to be opened and their rules.

The central instance does not need any network configuration to recognize the Web dispatcher.

Configure your network to direct all the user hits to reach the system hosting the web dispatcher.

web dispatcher then redirects these requests to the apps.

you can still access the sap apps using the browser by hitting their url directly.

but if you system has a firewall then probably you would be interested to open the wed dispatcher running port alone and get load balanced.

Remember, one functionality of the web disp is to act as a reverse proxy.