cancel
Showing results for 
Search instead for 
Did you mean: 

JRA and connection to SAP, load balancing

Former Member
0 Kudos

Hi.

I am trying to connect from xMII version 12 til SAP using JRA. Does anyone know a function call that enables me to se the exact servername or something like this, enabling me to verify whether I am connecting to an exact server or not?

Is it correct, that I need to specify these params when connecting to SAP Cluster?

MessageServer=b20main,

SystemID=B20,

Group=PUBLIC.

Somewhere I have seen that Group should be enough?

BR.

Poul.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Sam.

I got a little further, but not all the way yet. From JRA file, I think I need to replace ServerName with MessageServer along with a couple more. I also found a debug flag to set. And I found a message about adding a line to services file within c:\windows\system32\drivers\etc.

But not there yet. I am verifying my SAP data and when getting there, I will post the hints on this threat.

BR.

Poul.

0 Kudos

Poul,

Please let me know what you find and I will update the guide accordingly.

Sam

0 Kudos

Hi Poul and Sam,

Please do the following to enable the JRA in xMII 12 to use the message server and logon group to backend ERP:

In Backup ERP:

- Create logon group in SMLG transaction for the instances you want the xMII JRA to connect to.

xMII:

- Deploy SAPJRA.RAR

- Remove ServerName and PortNumber as you want to use the Message Server

- Add parameters: MessageServer, SystemID, and Group with values:

Message Server - Virtual Hostname of the backup system for cluster

SystemID - SID name of the backup ERP

Group - Logon group created in SMLG transaction

- In the xMII service file, add the entry "sapms<ERP SID> 36<system number of ERP>/tcp'.

- Stop and restart xMII. You will also need to stop and restart the windows service for xMII too.

Thanks,

Van Vi

Answers (2)

Answers (2)

Former Member
0 Kudos

A few more hints, the quick version

JRA via BLS logfiles are usually placed in

C:\usr\sap\<SID>\JC00\j2ee\cluster\server0\, in my case called dev_rfc.trc.

JRA Connections can be found and verified with the following tool.

http://localhost:port -> Web dynpro -> Web dynpro console -> Jco connection pools.

In Visual administrator -> Server0 -> Services -> Connector container -> Your JRA name. Select the connection name belov and select tab Managed connection factory, then properties.

Here you can add one of the following

Trace - Enable/disable trace on all middleware layers(true or false). On default is false.

TraceRFC - Enable/disable RFC trace (true or false). On default is false.

TraceJCO - Enable/disable JCO trace (0 for none, 10 for highest level). On default 0. Type Integer.

TraceJRA - Enable/disable JRA trace (0 for none, 10 for highest level). On default 0. Type Integer.

Which enables further logging, also found in the dir.

C:\usr\sap\<SID>\JC00\j2ee\cluster\server0\.

0 Kudos

Poul,

From what I know about the JRA, which is no very much, the group should be all you need...I mention this in the NW Install Pre-Release Guide that I sent to you.

Sam