Show TOC Start of Content Area

Procedure documentationSAP JRA Configuration on the Application Server Java  Locate the document in its SAP Library structure


Before you create a connection to an SAP system, a Resource Adapter instance should be configured for this system.

Each SAP JRA instance represents one SAP system. However, the same system may also be represented by several SAP JRA instances.

The AS Java is delivered with at least one deployed SAP JRA instance.




Basic Steps are:


  1. Configure Instance (no clone possible)  => all Resource Adapters
  2. Create factory => all ConnFactories
  3. Configure cloned factory => all ConnFactories
  4. Configure existing factory => all ConnFactories
Configuring a SAP JRA Instance

To configure a SAP JRA instance, proceed as follows:

       1.      Enter SAP NetWeaver Administrator and select Configuration Management -> Infrastructure -> Application Resources.

       2.      Select <All JCA Connection Factories> in the drop down menu Show <All Resources>

       3.      Select a suitable Connection Factory (the one always available is eis/SAPJRAFactory).

       4.      On the pane Configuration Properties you can set properties for outbound calls.


The easiest way to configure all needed connection properties is to configure the property DestinationName, where you enter the name of the Destination that has been configured via the Destination service. You can also override UserName and Password with the according parameters configured in the Destination, if needed. You can also configure all connection parameters directly on this ConnectionFactory instance.

When connecting to an SAP system the following properties are required:




        ServerName=<host name>



The corresponding field for Port Number  is named System Name in the SAP system and is a two digit number, for example “21”.

If you use a cluster of servers, the properties MessageServer, SystemID and Group should be used instead of ServerName and PortNumber. In this case a connection will be established to one of the currently running servers of this cluster.

Creating a Connection Factory (Client Scenario)

To create a new ConnectinoFactory configuration perform following steps: 

       1.      Choose Configuration Management -> Infrastructure -> Application Resources

       2.      Select All JCA Resources in the drop down menu Show <All Resources>

       3.      Go to SAPJavaResourceAdapter15 ->  Dependent JCA Connection Factories ->

Copy & Add new JCA Connection Factory.

       4.      Enter the JNDI name for your new ConnectionFactory, e.g. the system name, like "BCE".

       5.      Save your entries.

Configuring a Connection Factory

To configure the connection parameters proceed as follows:

       1.      Select JCA Connection Factory Details

       2.      Choose Configuration Properties to configure connection parameters.


The ConnectionFactory name that you have defined by cloning the SAP JRA instance is the JNDI name that you will be using in your application code for connection creation in the Client Programming Model.


The ConnectionFactory inherits the parameters configured on the corresponding Resource Adapter. Therefore, if the JRA is configured, the ConnectionFactory configuration does not need to be done separately. It will use the same DestinationName for connection creation (in the above example “BCE”).

Accessing an SAP Java Application from ABAP (Server Scenario)

If you want to access a Java application running on the AS Java from your ABAP application you will need to start server instances for JRA. To do this perform the following steps:

       1.      Select All Resource Adaptors in the drop down menu Show <All Resources>

       2.      Select a suitable Resource Adapter (already available one is SAPJavaResourceAdapter15).

       3.      On the pane Properties you can set up the configuration for inbound calls.

You need to configure at least the following properties:

    MaxReaderThreadCount=<number of listening servers>

    ProgramID=<program ID as configured in SM59>


When executing server calls (ABAP calls Java) also the connection parameters for client calls are required. This is needed to obtain the meta data information for incoming calls. In this case you have to specify also the property DestinationName.

Client and Server Calls

If you want to provide both client and server communication, configure at least the following properties on the Resource Adapter:




      GatewayServer (needed only if the destination is configured for load balancing or if an external Gateway is specified).

The server part of the SAP Java Resource Adapter passes received requests from SAP to the Message Driven Beans registered for this Resource Adapter instance (see Server Programming Model).

Further Information

For further information on the Programming model, see:

      Client Programming Model

      Server Programming Model




End of Content Area