Web dispatcher installation

[florian_royer]

hello sdn,

is the way I want to install three web dispatcher instances okay or is there a problem installing the web dispatcher which points to the system where it is installed?

On System1, all three webdispatchers and a web application server are installed.

url1:8011 -

---

> System1

url2:8012 -

---

> System2

url3:8013 -

---

> System3

if the user enters http://url1.company.com:8011, webdispatcher1 handles the request.

if the user enters http://url2.company.com:8012, webdispatcher2 handles the request.

if the user enters http://url3.company.com:8013, webdispatcher3 handles the request.

Edited by: Florian Royer on Apr 4, 2008 2:11 PM

Edited by: Florian Royer on Apr 4, 2008 2:15 PM

[Former Member · Accepted solution]

There is no problem installing 3 web dispatchers on one system.

Manitain 3 diff SID's and 3 diff System no.

If on unix system have 3 mount points.

Cheers

Shaji

[florian_royer · Accepted solution]

if so, why does the first webdispatcher not do anything but the second one works fine?!

(both should be correctly configured)

Edited by: Florian Royer on Apr 4, 2008 2:44 PM

[Former Member · Accepted solution]

This is very generic statment.

Do you mean the Web Disp 1 is not starting ?

This needs to be investigated. We need logs of webDisp1 to give you the right answer.

Can you give the information in detail.

Cheers

Shaji

[florian_royer · Accepted solution]

in the management console, the web dispatcher starts (it appears green).

but if i want to see the web administration tool, it is not possible: the administration tool is not available at http://<sapwebdisphost>:<port>/sap/wdisp/admin/default.html

dev_webdisp does also not show anything...?!

Edited by: Florian Royer on Apr 4, 2008 3:07 PM

[Former Member · Accepted solution]

This looks like more of memory issue !!!

Shutdown all webdispatchers and Restart Web dispatcher 1 only. What is the result? Then start web_disp2 and web_disp3

[florian_royer · Accepted solution]

I've already deinstalled all other web-dispatchers... there is only webdisp1 left.

[Former Member · Accepted solution]

Would advice you to uninstall this also and start again, shouldn't take long

or have a look at

Starting the SAP Web Dispatcher with the Bootstrap Option

http://help.sap.com/saphelp_nw70/helpdata/en/f6/3c0b0389cea34ba66f10d62b718a1a/frameset.htm

-

---

Starting the SAP Web Dispatcher

http://help.sap.com/saphelp_nw70/helpdata/en/f6/3c0b0389cea34ba66f10d62b718a1a/frameset.htm

-

---

Parameterization of the SAP Web Dispatcher

-

---

Troubleshooting

http://help.sap.com/saphelp_nw70/helpdata/en/f6/3c0b0389cea34ba66f10d62b718a1a/frameset.htm

[florian_royer · Accepted solution]

Thank you, but I already went through that documents.

I installed the webdisp from the installation dvd. after that I started the sapwebdisp -bootstrap and then started the web dispatcher via sap management console.

but I can't find the mistake I made, because I cannot even surf to the admin interface...

We thought there might be a problem with:

a) WebAs and Webdisp are installed on the same host

b) the given ports

Seems like b) is the problem... I reinstalled the webdisp with another port, now it is up.

But what about the memory thing?

Edited by: Florian Royer on Apr 4, 2008 4:44 PM

[Former Member · Accepted solution]

type ' netstat -ab ' to see if the ports are being used.

[Former Member · Accepted solution]

Hi,

Check the dev_webdisp web dispatcher trace file for errors.

You can also, if needed, increase the trace level from the sapwebdisp.pfl profile.

Regards,

Olivier

[florian_royer · Accepted solution]

hey guys, now I found out that the webdisps didn't run.

after executing sapwebdisp pf=sapwebdisp.pfl --> webdisp 1 is running.

then I thougt my problem is solved, closed the prompt-window and executed another one with webdisp 2 --> works.

but soon I realized, that now webdisp 1 is down.

Now I found out that all webdispatchers run after executing sapwebdisp... and not closing the prompt windows.

Is there any solution for that?

Edited by: Florian Royer on Apr 10, 2008 12:23 PM

[Former Member · Accepted solution]

Hi,

Are you telling us that you just launch the web dispatcher from a DOS command prompt window and that you close the window and think the web dispatcher willcontinue to run ?

If yes, I think you need to learn a little bit deeper how windows works !

You need to install the SAP web dispatcher as a Windows service for it to be able to run in the background and with no interactive session opened on the server.

Regards,

Olivier

[florian_royer · Accepted solution]

well, the major problem is that over mmc the wdisps appeared green (after start in the mmc). there was no reason for me to think that they are not up.

I know that I have to install them as a service, I just asked me why it didn't work over the mmc? it appeared green, but was not reachable.

[Former Member · Accepted solution]

Hi,

Don't believe all the green lights you may see : always check and double check, you will save a lot of time !

Regards,

Oivier

[florian_royer · Accepted solution]

thx a lot.

we found a solution.

the web dispatcher (as shown in the mmc) starts with a different profile - not with the sapwebdisp. so the port which we use to call the wdisp-admin-page is different (81$$ + sysnr), but in our case that is okay.

[Former Member]

Hi

I had the same problem and the solution was changing the profile parameter icm/server_port_XX = PROT=HTTP,PORT=XXXX (the port must be different that the message server port).

Regards