How to activate http for message server

[Former Member]

Just upgraded to ECC 6.

Result: ABAP CI DVEBMGSxx

no J2EE

no SCS (or ASCS or JSCS).

In the old 47 R3 Enterprise we had external ITS.

In ECC 6 (SAP NetWeaver 7.0) we have internal ITS via ICM.

We THINK we need to connect up sapwebdisp to internal ITS, but sapwebdisp wants to talk http to message server on port 81xx.

Having just upgraded, my message server talks on 36xx.

How do I get it to talk http?

Is this part of seperating out the SCS instance?

I am trying to avoid installing the J2EE addon.

Ken Chamberlain

University of Toronto

[Former Member · Accepted solution]

Hi,

you have to configure the Message Server HTTP port with the profile parameter

ms/server_port_0 =

PROT=HTTP,PORT=81$$,TIMEOUT=30,PROCTIMEOUT=600

$$ means the abap system number. this the default port.

Hope this helps.

Olivier

[Former Member]

Oliver has listed many good reasons why to use sapwebdispatcher. He forgot the best reason: emulating production.

I indicated at the beginning of this thread that I was playing with my sandbox system which was composed of a single CI. I realise I can contact directly to the CI's ICM without using sapwebdispatcher, but production ISN'T a single CI. I'd rather learn how to deploy sapwebdisp now with the sandbox system than a year or so from now when production is going live with SAP NetWeaver 7.

/Ken

[Former Member]

Hi!

Big thumbs up for that one! It's one of the typical things people argue about. It's absolutely mandatory from my point of view to have the same level of complexity in the QA Environment that you have in the prod environment, meaning to say: If you have loadbalancing in the P use it in Q as well, if you have secodary application servers in P have at least one in Q as well...

Regards,

Jörg

[Former Member]

Hi Ken

Yes of course !

As I use the Webdispatcher on the production system, I have also installed it on all the landscape systems (dev, quality, pré-production, testbed).

Olivier

[Former Member]

Hi!

Why do you need the Webdispatcher if you're only running a CI? In fact the http connect from the enduser typically goes to the ICM for which you need to assign the http-Port you want (if you want to use a port <1024 you will have to use ExternalBind on Unix). When ICM is configured correctly you need to activate the desired services in TA sicf.

If you want/need the sapwebdisp in your environment you need to either make the MS speak http (like Olivier suggested) or you need to make the sapwebdisp read the list of available application servers from a file, which has the disadvantage of not being dynamic, so the sapwebdisp will not know (best to my knowledge) when one of the ASs is down.

Hope this helps,

Jörg

[Former Member]

You can do a lot of things with the Webdispatcher :

use the standard HTTP 80 and HTTPS 443 ports

load balancing

filter the URLS

filter the IP adresses

configure redirect rules

get specific HTTP logs

protect from malicious scripts

manage HTTPS load instead of the ICM

ans so on....

There are many good reasons to use the Webdispatcher, it's a very interesting tool !

Regards,

Olivier

[Former Member]

Hai,

You can get all the dispatcher ports and your message service port in the "Services"

File, this will be available in the directory " C:\WINDOWS\system32\drivers\etc\services "

and also check the http service of your Web AS ABAP by using the tcode 'SMICM'. there you click the services button it will show your http and SMTP services.

regards,

Gopinathan.

[Former Member]

I guess you wouldn't have http functionality without the Java add-on.

I hope this helps

tamilboy

[Former Member]

I'm trying to avoid the java add-on. It's a pain in the ___!

I virtually attended TechEd 07. Even SAP is saying don't install java if the solution doesn't require it.

I found note 821904 with a script to create the ASCS.

Now to see if sapwebdisp gets any useful information out of the ASCS. There seems to be a LISTEN now on port 81<ASCS instance no>.