Web Dispatcher configuration (ABAP+Java vs. ABAP+Portal)

[Former Member]

We are using an internal Web Dispatcher to allow the connections from different networks.

This Webdispatcher entry we add to WAS configuration within Portal system object

By defintion of ABAP+Java double stack we do not have any problems and the test

http://webpispatcher:port/sap/bc/ping is successful.

When we have a ABAP system + Portal (Java) we only can test the connection

http://webpispatcher:port/

When we execute the test

http://webpispatcher:port/sap/bc/ping we get an error, because the url goes to Java stack.

We also detected that on Web Dispatcher configuration for ABAP+Java we have ABAP and J2EE server groups and application servers.

For ABAP+Portal we have only J2EE groups on Web Dispatcher configuration.

Question:

Which SAP parameter (e.g. ms/server_port_0, icm/HTTP/j2ee_0) or Web Dispatcher parameter (ms/http_port) is responsible for generation of ABAP groups (e.g. PUBLIC) within Web Dispatcher?

[Former Member · Accepted solution]

Hi,

If your Web dispatcher release is under 7.2, you need 2 separate Web dispatchers : 1 for the Java system and 1 for the abap system Because before release 7.2 the web dispatcher can only connect to one single message server http port.

It works for a dual stack system because the ICM is able to route java URL to the java stack.

Regards,

Olivier

[nelis]

Which SAP parameter (e.g. ms/server_port_0, icm/HTTP/j2ee_0) or Web Dispatcher parameter (ms/http_port) is responsible for generation of ABAP groups (e.g. PUBLIC) within Web Dispatcher?

In ABAP the logon group is handled by the ICF. In SICF you specify within the actual services(properties) which logon group that service should use for load balancing. As far as I remember though there is an exception if you are using an "end-to-end" ssl configuration where you can specify the destination logon group using wdisp/HTTPS/dest_logon_group parameter.

rdisp/mshost is the parameter on your web dispatcher that points to your message server to get a list of available logon groups.

Nelis

[Former Member]

Hello!

When I go to Web Dispatcher Administration http://Webdispatcher:Port/icmadmin/

(path Dispatching Module --> Monitor Application Servers --> Application Server Monitor --> List of JAVA Hosts) I can detect the following settings within HTTP conn pool column:

Port 50100

max 500

current 1

peak 3

The standard value of Port (50100) is wrong and should be changed to 8000.

Question:

Is that a Portal profile in SAP or a Web Dispatcher profile?

[nelis]

Is that a Portal profile in SAP or a Web Dispatcher profile?

As you showed that is your Java host systems port and which ever system uses '01' as its system number. I don't think it is incorrect.

Nelis

[Former Member]

Yes, but how can I change this setting from 50100 to 8000?

Because all the requests with /sap/bc/... should go port 8000 not to port 50100..

Thank you!

[nelis]

If you are not going to be using the web dispatcher to connect to a Java Host then you can set the parameter is/HTTP/default_root_hdl to 'abap'. It is likely this is set to 'java' which would handle the http requests differently.

You don't have to configure the ICM ports used by your ABAP server on the web dispatcher, it picks up this information from the message server(metadata exchange) which must be configured to accept HTTP requests.

I suggest you read through the [SAP Web Dispatcher Documentation.|http://help.sap.com/saphelp_erp60_sp/helpdata/EN/42/5cfd3b0e59774ee10000000a114084/frameset.htm]

Nelis