Parameters for SAP JRA Configuration 
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 installation
SNC connections
Parameter |
Description |
|---|---|
General Parameters |
|
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 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 is "false", the COMMIT is managed by the calling application. |
MultiRepository |
To manage calls of multiple SAP systems that are set up on different rpository 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 value = 3. |
GatewayServer |
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 Parameters |
|
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. |
Add-on installation |
|
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 the 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 value = 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>. |