SAP JRA Configuration on the SAP J2EE
Application Server 
Before you can create a connection to a particular SAP system, you have to configure a Resource Adapter instance for this SAP system. Each SAPJRA instance represents a single SAP system. A SAP system can also be represented by several SAPJRA instances.
The configuration steps are described below:
...
1. Create an SAPJRA instance for a particular SAP system using the SAP J2EE Engine
Administrator’s Connector Service.
The SAP J2EE Engine is delivered with at least one deployed SAPJRA instance. Once you have entered a Connector Service you can clone/copy one of the available SAPJRA instances (in the name of the Resource Adapter instance you will see an *SAPJRA* string).
2. After cloning it you can set connection parameters according to the requirements of the target SAP system.
You can find a description of the required connection properties in the SAPJRA instance that is displayed in the Connector Service.
At least the following properties are required to connect to a standalone SAP system:
· SAPClient=XXX
· UserName=***
· Password=***
· ServerName=<host name>
· PortNumber=XX, which is known in SAP as system number, and for example has value 21 for the system B20.
If you use a cluster of servers the properties MessageServer, SystemID and Group should be used instead of ServerName and PortNumber (for additional information, see the description of the SAPJRA instance in the Connector Service or in the file ra.xml). In this case a connection to one of the currently running servers of this cluster will be established. The configured Message Server decides which server the call will be directed to.
You can find the list of all possible configuration properties in the description of the SAPJRA instance in the Connector Service.
The Connection Factory name that you have defined by cloning the SAPJRA instance is the JNDI name that you will subsequently use in the coding for creating a connection in the Client Programming Model.
Further Information
For further information on the Client Programming model, see: