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

Question

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?

Answer 1

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