Start of Content Area

Background documentation Parameters for SAP JRA Configuration  Locate the document in its SAP Library structure

In the following table you can get an overview of the parameters that you can use when configuring the SAP JRA. The parameters are divided into the following categories:

      General parameters

      Parameters for inbound communication

      Optional parameters

       Tracing and logging

       Add-on installations

       SNC connections

 

 

SAP JRA: Configuration Parameters

Parameter

Description

DestinationName

Name of the destination for client calls (Java calls ABAP) that was defined in the J2EE Destination Service. Repository metadata refer to this.

or (Using JRA Configuration)

 

ServerName

SAP application server, for example, is0008

PortNumber

SAP system number, for example,  01

SAPClient

SAP client, for example, 001

Language

Logon language, for example, EN

UserName

Logon user

Password

Logon password

MessageServer

SAP Message Server when using a server group (instead of ServerName/PortNumber), for example, binmain

SystemID

SAP system name, for example,  BIN

Group

Group of SAP

application servers, for example, PUBLIC

AutoCommit

Activates/deactivates JRA COMMIT function. If the value true (default) is set, the JRA triggers a COMMIT after every call to an SAP backend system. If the value false is set, the COMMIT is managed by the calling application.

MultiRepository

To manage calls of multiple SAP systems that are set up on different repository destinations. An enhancement to the DestinationName function.

 

Parameters for Inbound Communication (Definition Using JRA Configuration)

 

ProgramID

Program ID of the called server. A destination with this program ID is configured using transaction SM59.

MaxReaderThreadCount

Optional. Maximum and initial number of listening servers. Default = 3

GatewayServer

Optional. Default value = <ServerName>. Configure this parameter with the same value that is defined in transaction SM59 for the gateway host.

GatewayService

If you are using a gateway host that does not belong to the system where you maintained the parameter above, you also have to define the GatewayService parameter.

BindingKey

Optional. If you maintain this parameter for the JRA and MessageDrivenBeanEnable with the same value, this produces a binding between the JRA instance and the MessageDrivenBean. Then this MessageDrivenBean is only registered in the relevant Resource Adapter.

 

 

Optional Properties:

 

For Tracing and Logging

 

TraceJRFC

Activate /deactivate the JRFC trace (true or false) Default value = false The parameter is valid for a Virtual Machine.

TraceRFC

(true or false). Default value = false The parameter applies for all connection that are created by a ConnectionFactory.

TraceJCO

Activate/deactivate the JCO trace (0 for “no trace“, 10 for the highest level). Default value = 0. type integer. The parameter is valid for a Virtual Machine.

TraceJRA

Activate/deactivate the JRA trace (0 for “ no trace“, 10 for the highest level). Default value = 0. type integer. The parameter is valid for a Virtual Machine.

 

 

For Add-on Installations

 

Local

Local J2EE Gateway. The parameter is only relevant if a double stack communication (Java/ABAP) is taking place. Type: Boolean Default value = false

 

 

For SNC Connections

 

SNC

Activate/deactivate SNC communication (true or false) Type: Boolean Default value = false

SNCPartnerName

SNC partner name. for example, "p/secude:CN=B20, O=SAP-AG, C=DE"

SNCLevel

Optional. Security level of SNC connection (1 to 9). Default = 8

SNCMyName

Optional. Overwrites default-SNCcaller names, for example, "p:CN=I0XXXXX, O=SAP-AG, C=DE"

SNCLibPath

Optional. Path and file name of the SNC Library Default value = <Library defined by system>.

 

 

 

End of Content Area