Questions regarding R/3 Integration with Load Balacing

[Former Member]

Hello,

I implemented the SAP GUI Transaction Iview successfully to an R/3 backend with Load Balancing.

Now I have two questions which I hope you can answer

1) What Web As hostname do I have to enter to use the load balacing of the R/3 backend? I am afraid to use only one dedicated Web As but I don't know what to type in to be sure that R/3 uses the load balancing

2) To facilitate SSO from the Portal to our dedicated R/3 I inserted the instance parameters

login/accept_sso2_ticket 1

login/create_sso2_ticket 2

Where do I have to insert these parameters in our load-balancing backend? At our central instance? At the message server? At all connected Application Servers?

Thank you very much in advance for your help.

Rewarding points are guaranteed.

Philipp

[Former Member · Accepted solution]

Hi Philipp,

1) Enter the your loadbalancing server as WebAS adress - which is the SCS host with the message server.... Also enter the port of the message server: 81XX where XX is the system number of the SCS

2) Enter the parameters to the DEFAULT.PFL in transaction RZ10.

Then they are valid for all application servers...

Hth,

Michael

[Former Member · Accepted solution]

Thanks for answering so quick.

Regarding answer 2: Thank you very much. I will let the parameters insert and active after reboot

Regarding answer 1:

Within the portal and the system definition I inserted a FQDN as a Message-Server Address (e.g. my.company.com)

If I get you right I have to use this address as the Web-AS-Address, too, combined with the Message Server Port based on the system number, right?

Ok, now I am not real Basis guy. With dedicated servers I can get to the system number via the properties in the SAP GUI, but I don't see the system number in the SAP GUI with this load balanced server.

Can you tell me where to read out the System Number of the message server??

Thanks once more,

Philipp

[Former Member · Accepted solution]

In the <b>SAP Management Console (MMC)</b> you see the Server Central Services (SCS) and the Dialog Instances (DI) / Application Servers.

The SCS and therefore the message server FQDN as well as the port number can be found in the trace file of the message server itself:

>> open the SAP MMC

>> navigate to the SCS server

>> it shows msg_server.exe and enserver.exe as processes

>> right-click the msg_server.exe

>> choose Developer Trace

It shows something like this:

-

---

trc file: "dev_ms", trc level: 1, release: "700"

-

---

[Thr 6244] Thu Aug 16 13:24:08 2007

[Thr 6244] MsSSetTrcLog: trc logging active, max size = 20971520 bytes

systemid 560 (PC with Windows NT)

relno 7000

patchlevel 0

patchno 98

intno 20050900

make: multithreaded, Unicode, optimized

pid 8852

[Thr 6244] ***LOG Q01=> MsSInit, MSStart (Msg Server 1 8852) [msxxserv.c 1824]

[Thr 6244] load acl file = \usr\sap\<SID>\SYS\global\ms_acl_info.DAT

[Thr 6244] MsGetOwnIpAddr: my host addresses are :

[Thr 6244] 1 : [172.27.XX.XX] SERVER.DOMAIN.COM (HOSTNAME)

[Thr 6244] 2 : [127.0.0.1] SERVER.DOMAIN.COM (LOCALHOST)

[Thr 6244] 3 : [172.27.XX.XX] SERVER.DOMAIN.COM (NILIST)

[Thr 6244] MsHttpInit: full qualified hostname = <b>SERVER.DOMAIN.COM

>>> the server FQDN</b>

[Thr 6244] HTTP logging is switch off

[Thr 6244] set HTTP state to LISTEN

[Thr 6244] MsHttpOwnDomain: own domain[1] = SERVER.DOMAIN.COM

[Thr 6244] ms/icf_info_server : deleted

[Thr 6244] *** I listen to internal port 3900 (3900) ***

[Thr 6244] *** HTTP <b>port 8100</b> state LISTEN ***

<b>>>> the port number</b>

Hth,

Michael

[Former Member · Accepted solution]

Hi Michael,

unfortunately our load-balanced server is no fance Netweaver 7.0 Machine on windows but a Release 620 on Solaris.

So there is no J2EE or an MMC console.

Nevertheless I used st11 to see the traces there, but there is nothing like a dev_ms

A lot of dev_w1 -> dev_w12 or a dev_icm and so on.

I assume that there is something fundamental missing?

Philipp

[Former Member · Accepted solution]

OK, 6.20 is kind of different...

Hm, what about transaction SMMS?

Should give you the option to check the message server parameters including the hostname and port...!? Hopefully

(How do you access the loadbalanced system via SAPGui? With a direct application server connection??)

Michael

[Former Member · Accepted solution]

Hi Michael,

this is what SMMS -> Goto -> Parameters gives me

Parametereinstellungen des Message Servers

Release = 640

Release no = 6400

Trace level = 1

System name = PF1

comment = message server PF1

start time = Sat Jun 16 14:18:33 2007

start time (seconds) = 1181996313

build time = Oct 28 2006 09:27:49

build with Unicode = FALSE

build with Threads = TRUE

system type = Solaris on SPARCV9 CPU

system id = 0x172

server host = nispp652

server host (fqn) = nispp652

server addr = 192.168.1.45

server service = sapmsPF1

server port = 3600

J2EE send notification = message/request

J2EE advanced login = on

J2EE broadcast time = 0/Thu Jan 1 01:00:00 1970

J2EE reconnect support = 1

ms/timeout = 5000

ms/timeout2 = 10000

ms/conn_timeout = 300

ms/max_sleep = 20

ms/keepalive = 300

ms/max_clients = 300

#clients = 15

ms/max_counter = 100

ms/max_vhost = 16

ms/max_queue = 300

ms/warn_queue = 5

ms/cache_check = 900

cache count = 6

cache size = 25

allocated buffer = 166

ms/max_open_requests = 10000

#max_open_requests = 0

Can you see something from this?

I access the load-balanced server via SAP Gui after someone installed this on my machine.

He added something in my c:\WINDOWS\SYSTEM32\DRIVERS\ETC\SERVICES files

The properties of my SAPGUI for that machine shows me

Connection Type: Group/Server Selection

Description: PF1

System ID: oo

Message Server: 192.168.1.4

SAProuter: <empty>

Group/Server: DEFAULT

System Number: 17 <- This field is greyed-out

[Former Member · Accepted solution]

Hi,

message server schould be <b>nispp652</b>

Do a ping to IP 192.168.1.4 and check the output. Should be the servername from above...

Systemnumber seems to be "00"...

Or give "17" a try if "00" is not working...

Michael

[Former Member · Accepted solution]

Thank you! Now it's working!