Configuring Logon groups for JAVA instances using NWA method

[Former Member]

Hello,

we have a BI dual System landscape ( CI ABAP+ JAVA plus 2 dialog instance ABAP+JAVA, based on NW04s. I have set up a Web Dispatcher to do a load balancing for JAVA instances. I configured the logon groups according this documentation using NWA (http://help.sap.com/saphelp_nw04/helpdata/en/45/3dbe11a82b6bf1e10000000a1553f6/content.htm).

The following points are still quite unclear for me:

1. according documentation I should specify the following profile parameters:

[Define the special HTTP URLs, which SAP Web Dispatcher uses to send to the AS Java to retrieve the logon groups information]

wdisp/J2EE/group_info_location = [?] /JavaEE/public/icf_info/icr_groups

wdisp/J2EE/url_map_location = [?] /JavaEE/public/icf_info/icr_urlprefix

Wich values should i take here actually? These one or /J2EE/icr_groups and /J2EE/icr_urlprefix ?

2. Also I have to configure (in visual administrator) the GroupInfoRequest and UrlMapRequest properties of the HTTP Provider service running on server processes. They recommend to use /J2EE/icr_groups and /J2EE/icr_urlprefix. Should it be the same values as defined in those profile parameters?

3. I have defined the instance IDs and exacte Alias in the groups definitions in nwa. Is it possible to proof somehow while using my URL http://<host>:<port>/TestApp~test/<application_resource>; either im web dispatcher (traces?) or on a web site on which DI I actually land to be sure that my load balancing works properly and i don't land on my Central Instance?

Thanks a lot in advance for your advices.

best regards,

Polina

[Former Member]

Understood, Install the web dispatcher and configre the ABAP Message Server Port and ms/http_port (T-CODE:SMMS). Test this link

http://host:port/sap/public/icf_info/icr_groups

and this would retrieve the list of ABAP (SMLG) cofigured groups.

For java load balancing, icm of that host will send the incoming requests to JAVA Dispatcher. The load balancing happens on the basis of server nodes and can be found in the web dispatcher session dispatching table.

There are no necessary parameters required for java load balancing except the number of server nodes you'll hookup to that dispatcher.

There is an option called service based, where we configure the j2ee hosts to accept the connections for the services which are running but I haven't seen much customers using this option.

Bottom line: No changes are required for java side and enable the "ext rfc" option for abap logon groups and rest will be taken care by Web Dispatcher.

Use connection pooling and high timeouts to acheive the better througput and use the SSL termination on Web Disp.