cancel
Showing results for 
Search instead for 
Did you mean: 

Web Dispatcher

florian_royer
Participant
0 Kudos

Hello experts,

we have installed two web dispatcher instances, pointing at two different servers.

One works fine, the other one doesn't.

The second one, if we want to surf to http://<server>:<port>/irj/portal, the server+web dispatcher do not even repeat. We receive an empty page, without code or an error message.

Surfing to the same page directly, everything works fine.

In the web administration tool, the server is visible, pingable, and so on...

Any idea why we receive an empty page?

Thx a lot, Florian

Accepted Solutions (0)

Answers (2)

Answers (2)

Benny
Product and Topic Expert
Product and Topic Expert
0 Kudos

Are theses servers different systems too?

Remember that Web Dispatcher connects to the message server and gets its information from there.

Are both of the servers are portals?

Can you connect anything else on the second server (like the entry page usually on <server>:50000)?

Regards,

Benny

florian_royer
Participant
0 Kudos

These two Dispatchers point at two completely different systems. The only thing they have in common is that they are installed on the same host.

Yes, both systems are portals, but different ones. One web dispatcher is working fine, until now no problems occured.

But the second instance doesn't display the portal, no error message declaring why - a completely white page without any content. Surfing to that portal the "normal" way (<host>:<port>) everything works fine.

Edited by: Florian Royer on Mar 28, 2008 1:44 PM

Benny
Product and Topic Expert
Product and Topic Expert
0 Kudos

OK. What I asked was if you can connect to the server without calling portal. That means to call <server>:50000 instead of <server>:<port>/irj.

Maybe you have manipulated this via web dispatcher already, as it can be configured to go directly to that call no matter what the browser calls. In that case Id ask you to change this or post the web dispatcher configuration file (standard would be sapwebdisp.pfl)

Regards,

Benny

Former Member
0 Kudos

Hi Benny

Even,I am facing the same problem i.e one dispacther is not working.

Do I need to check at ICM side.

Please could you adivse me some steps.

Thanks

Sukrut S

Benny
Product and Topic Expert
Product and Topic Expert
0 Kudos

No I cannot.

"Steps" won't help you. Please describe what is your problem and the symptoms of it, then I may be able to help.

Step by step descriptions are for beginners. If you are a beginner you are working in the wrong place.

Regards,

Benny

florian_royer
Participant
0 Kudos

No, I cannot connect to the server, but webadmin-page works fine.

Web dispatcher one (works fine)

WD1_W00_phwsmh01s01


SAPSYSTEMNAME = WD1
SAPGLOBALHOST = phwsmh01s01
SAPSYSTEM = 00
INSTANCE_NAME = W00
DIR_CT_RUN = $(DIR_EXE_ROOT)\$(OS_UNICODE)\NTI386
DIR_EXECUTABLE = $(DIR_CT_RUN)
#-----------------------------------------------------------------------
# Accesssability of Message Server
#-----------------------------------------------------------------------
rdisp/mshost = phoron01s.phoron.local
ms/http_port = 8103
#-----------------------------------------------------------------------
# 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$$

sapwebdisp


# Profile generated by sapwebdisp bootstrap

# unique instance number
SAPSYSTEM = 1

# add default directory settings
DIR_EXECUTABLE = .

DIR_INSTANCE = .

# Accessibility of Message Servers
rdisp/mshost = phoron01s.phoron.local
ms/http_port = 8103

# SAP Web Dispatcher Parameter
wdisp/auto_refresh = 120
wdisp/max_servers = 100

wdisp/shm_attach_mode = 6

# 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

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

icm/server_port_1 =

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

Web dispatcher two

WD2_W01_phwsmh01s01


SAPSYSTEMNAME = WD2
SAPGLOBALHOST = phwsmh01s01
SAPSYSTEM = 01
INSTANCE_NAME = W01
DIR_CT_RUN = $(DIR_EXE_ROOT)\$(OS_UNICODE)\NTI386
DIR_EXECUTABLE = $(DIR_CT_RUN)
#-----------------------------------------------------------------------
# Accesssability of Message Server
#-----------------------------------------------------------------------
rdisp/mshost = iwdfvm2160.wdf.sap.corp
ms/http_port = 8110
#-----------------------------------------------------------------------
# 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$$

sapwebdisp


# Profile generated by sapwebdisp bootstrap

# unique instance number
SAPSYSTEM = 1

# add default directory settings
DIR_EXECUTABLE = .

DIR_INSTANCE = .

# Accessibility of Message Servers
rdisp/mshost = iwdfvm2160.wdf.sap.corp
ms/http_port = 8110

# SAP Web Dispatcher Parameter
wdisp/auto_refresh = 120
wdisp/max_servers = 100

wdisp/shm_attach_mode = 6

# 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

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

icm/server_port_1 =

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

Benny
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello Florian,

how come, that your Message server runs on

rdisp/mshost = iwdfvm2160.wdf.sap.corp

This would be a machine at SAP. Unless you are one of my colleagues this should be completely wrong.

Additionally the instance numbers are 00 and 01. Unless this is handmade an installation would first make an SCS instance and then a server and give each a name, which would at least be 00 and 01.

Therefore the question: Did you install two times or only once and tried to copy anything?

Regards,

Benny

florian_royer
Participant
0 Kudos

iwdfvm... is a preconfigured and installed server by sap for us - named discovery server.

we installed two webdispatcher instances, twice via sapwebdisp -bootstrap.

Benny
Product and Topic Expert
Product and Topic Expert
0 Kudos

So, you're working with a discovery server...It would have helped to mention this a little bit earlier....

Nevertheless with that value the web dispatcher cannot work, as it will try to connect exactly to this server in exactly this domain aka sap.corp, which you cannot connect as you're outside the firewall. It works inside the virtual machine as this one will virtualize the values to the outside world.

With that in mind, I can assure you that you are looking forward to some massive reconfiguration of your system. It would be better to install both systems from scratch - even I'm not sure if this configuration will work at all.

Maybe the faster way is you tell me what you want to achieve at all and we discuss whether this is done in some other way.

Regards,

Benny

florian_royer
Participant
0 Kudos

we would like to achieve as follows:

exampledomain1.company.com --> || FIREWALL || --> WebDisp1 --> Application1

exampledomain2.company.com --> || FIREWALL || --> WebDisp2 --> Application2

On the not working webdisp: why does this work: http://<webdisp>:<port>/<application>; (in this case abap) ?

Former Member
0 Kudos

may be you can hardcode the port nos.

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

PORT=81$$ - > 8100 and 8101

Benny
Product and Topic Expert
Product and Topic Expert
0 Kudos

So you're saying what does not work is to call the portal, but calling an ABAP application does work?

That sounds strange to me, as web dispatcher gets all information of the back staging system from this servers message server. The message server you are calling is on a non working network address. So whatever you call on this web dispatcher

In the manuals in section:

[Web Dispatcher|http://help.sap.com/saphelp_nw70/helpdata/EN/42/5cfd3b0e59774ee10000000a114084/frameset.htm]

You can find this chapter for Web Dispatcher Administration:

[Using the Web Administration Interface|http://help.sap.com/saphelp_nw70/helpdata/EN/4f/3bee29d9764e988bdeecdb4d484722/frameset.htm]

Try this and check where you are connected. Once the Web Dispatcher starts up it should connect to a message server (As I said) and get the list of available servers. this you should be able to check with the monitoring.

Let's see what it comes up with. You then should also find out what ABAP server you called and I'm pretty sure this cannot be the one of the discovery server... But let's see.

Regards,

Benny

florian_royer
Participant
0 Kudos

We are not connected to the same server.

Benny
Product and Topic Expert
Product and Topic Expert
0 Kudos

Sorry, I don'T get what you mean with your last message....

Benny
Product and Topic Expert
Product and Topic Expert
0 Kudos

I forgot to complete a sentence in the last post:

So whatever you call on this web dispatcher... should be ignored or give an error.

Sorry for that.

Former Member
0 Kudos

I cannot believe the simple problem shooting steps have not been specified. This should have been done by anyone trying to help these poor people.

Basically the web dispatcher talks to the message server and gets back a list of servers that can be talked to and their ports. This can be checked in your case (ideally from phwsmh01s01) with the following commands

WD1 Test - should work

http://phoron01s.phoron.local:8103/msgserver/text/logon

WD2 Test - may fail

http://iwdfvm2160.wdf.sap.corp:8110/msgserver/text/logon

If WD2 fails then there is an issue with the web dispatcher connecting to the right port for the message server or the message server is not getting a list of instances that will talk the correct protocol.

If WD2 works then I would ensure the web dispatcher administrator is installed and check what responses you get with a trace level of 2 (or 3 if you want the whole URL) although to be honest it is likely that it is a J2EE problem.

I have seen problems lately where the portal is an add-in...it is when the J2EE does not talk correctly to the ICM, in this case a J2EE patch often fixes, there is a note. This is a good one as it does return a blank page.

Otherwise, I would check in the default.trc and various logs in the server log subfolder on the J2EE for starters before upping trace levels there.

florian_royer
Participant
0 Kudos

@Benny - we thought you mean that we are connected to the same server.

@Graham - both WDs "work". we also think that there could be a problem with the j2ee-engine. which note do you mean? one about patching j2ee or about receiving a blank page? I found one that could resolve our problem - note nr. 1048692.

This is the generated output after clicking on each link:

WD1


version 1.0
phoron01s_PC2_03
DIAG	phoron01s.phoron.local	3203	LB=5
RFC	phoron01s.phoron.local	3303	
HTTP	phoron01s.phoron.local	8000

WD2


version 1.0
iwdfvm2160_ERP_10
DIAG	iwdfvm2160.wdf.sap.corp	3210	LB=5
RFC	iwdfvm2160.wdf.sap.corp	3310	
HTTP	iwdfvm2160.wdf.sap.corp	51080	
SMTP	iwdfvm2160.wdf.sap.corp	25001	
J2EE	iwdfvm2160.wdf.sap.corp	51000	LB=1
J2EES	iwdfvm2160.wdf.sap.corp	51001	LB=1

Edited by: Florian Royer on Apr 1, 2008 10:24 AM

Benny
Product and Topic Expert
Product and Topic Expert
0 Kudos

Florian,

OK, that was a shorter way to the same list.

How did you call the iwdf... server?

From inside the machine where the VMWare is sitting?

Oh, and just to make sure: your discovery server is not hosted by SAP but running in your house?

Regards,

Benny

florian_royer
Participant
0 Kudos

The discovery server is not hosted by sap - it is in our house.

Both servers are in the same IP-range, without a firewall between them.

Benny
Product and Topic Expert
Product and Topic Expert
0 Kudos

Sorry that I have to ask again, but usually a discovery server is running on VMWare.

Is that the case???

If so: What is the network configuration of your VMWare (NAT,Bridged,Host-only).

Otherwise I'm a little bit on the wrong track...

Regards,

Benny

florian_royer
Participant
0 Kudos

No, it is not running on a VMWare.

Benny
Product and Topic Expert
Product and Topic Expert
0 Kudos

Now we're getting closer.

Please try calling http://iwdfvm2160.wdf.sap.corp:51000/irj/portal

That should show if your portal is running.

florian_royer
Participant
0 Kudos

That's what I meant with

Surfing to the same page directly, everything works fine.

at the beginning of this thread.

The portal is up and visible through http://iwd..:51000/irj/portal.

Edited by: Florian Royer on Apr 1, 2008 2:43 PM

Benny
Product and Topic Expert
Product and Topic Expert
0 Kudos

OK. I assume that the problem also appears if you call the Web dispatcher server on port 8101.

Together this means:

-Your Web dispatcher is configured to listen on port 8101 for http

-The message server is available under the server (iwdf...) and port (8110) that is configured for Web dispatcher

- Message Server does deliver the right values that you can use to connect to the portal directly (iwdf.... port 51000)

This is exactly how it should be.

The only way to check this is now to use the Web Administration Interface and check in there what is wrong here. All values seem to be set correctly. The only way now is to check online if those values actually have been set.

Please read through [Using the Web Administration Interface|http://help.sap.com/saphelp_nw70/helpdata/EN/4f/3bee29d9764e988bdeecdb4d484722/frameset.htm] and check if all those values are actually online.

Regards,

Benny

florian_royer
Participant
0 Kudos

Parameters have these values:

icm/server_port_0 --> PROT=HTTP,PORT=8101

ms/http_port --> 8110

under "monitor server groups":

hostname: iwdfvm2160.wdf.sap.corp

http-conn-pool: port 51080

Benny
Product and Topic Expert
Product and Topic Expert
0 Kudos

I'm at the end of my knowledge.

You should contact support for this. Don't know what this could be.

Regards,

Benny

florian_royer
Participant
0 Kudos

The above mentioned Help Note Nr. 1048692 solved the problem.

Now both web dispatcher are up and working!

It was a problem in the j2ee-engine with incoming http-requests.

THX a lot to you all!

Edited by: Florian Royer on Apr 2, 2008 6:38 PM

Former Member
0 Kudos

Hi,

Did you install the 2 web dispatchers on the same host ?

If yes, are they configured to listen on different ports ?

Regards,

Olivier

florian_royer
Participant
0 Kudos

Yes. They are running on a virtual server - but listening to different ports.