J2C connection factory properties

J2C connection factories configure an outbound connection to a target SAP instance. These properties correspond to the ManagedConnectionFactory interface of the J2EE Connector Architecture Specification.

A J2C connection factory manages connection pooling. It provides configuration information for outbound connectivity to a single SAP system instance from an application via the adapter.

The following table defines the SAP adapter-specific configuration properties that pertain to a J2C connection factory.

J2C connection factory properties

Property Type Globalized Description

ABAPDebug

String No Specifies whether the adapter invokes the ABAP Debugger for the appropriate function module when the adapter begins processing a business object. When set to true, the adapter opens the ABAP Debugger. Debugging requires a dialog user with proper user authorizations. You can add breakpoints only after the debugger opens. Important: This property should always be set to false in a production environment. The default value is false.

ApplicationServerHost

String Yes When configuring the adapter to run without load balancing, specifies the IP address or the name of the application server that the adapter logs into. In both cases, the adapter assumes that the name of the gateway host is the same as the value specified for this property.

Client

Integer No SAP Client number under which the adapter logs in, often 100.

Codepage

Integer No In order to establish a connection in the appropriate language, must correspond to the value specified in the Language property. For example, if Language is set to JA (Japanese), then Codepage must be set to 8000, as dictated by the SAP application. Refer to SAP documentation for the exact Language and Codepage values.
EIS BiDi Format String   The bi-di format used by SAP for its business data. The adapter normalizes the SAP bi-di data to the application server’s logical left-to-right bi-di format for inbound communication and from the application server’s format back to SAP bi-di format for outbound communication.
EIS Bidi Special Format String   Signifies a category of values that are subject to special treatment during invocation of bi-di transformation to ensure accurate transformation of the category. Categories are predefined. For example: FTP URLs and email addresses.

GatewayHost

String Yes Host where the gateway service is running. (This property is set via the administrative console, and not during adapter deployment via the enterprise service discovery wizard.)

GatewayService

String No Gateway server identifier; often sapgw00. The system number of the server running the SAP Gateway (usually an application server) is 00. The value cannot be 00 if there is more than one server. The default is sapgw00. (This property is set via the administrative console, and not during adapter deployment via the enterprise service discovery wizard.)

Group

String No When configuring the adapter for load balancing, specifies the name of the logon group that represents a group of application servers. (This property is set via the administrative console, and not during adapter deployment via the enterprise service discovery wizard.)

Language

String No Language in which the adapter logs in. The default is E, for English.

MessageServerHost

String Yes When configuring the adapter for load balancing, specifies the name of the message server. (This property is set via the administrative console, and not during adapter deployment via the enterprise service discovery wizard.)

Password

String Yes Password for the adapter’s user account on the SAP system. If bidirectional language support is enabled, this property is affected by the following BiDi properties, which are set using the enterprise service discovery wizard:
  • Password BiDi Format: Controls the bi-di format for this property.
  • Skip BiDi Transformation for Password: Controls invocation of bi-di transformation for this property.
Password BiDi Format String   Controls the bi-di format for the Password property.

RFCTraceOn

boolean No Specifies whether or not to generate a text file detailing the RFC activity for each listener thread. You can specify a value of true or false. A value of true activates tracing, which generates a text file. Use these text files in a development environment only, because the files can grow rapidly. The default is false. (This property is set via the administrative console, and not during adapter deployment via the enterprise service discovery wizard.)

SAPSystemID

String No When configuring the adapter for load balancing, specifies the logical name of the SAP system, which is also known as R3name. (This property is set via the administrative console, and not during adapter deployment via the enterprise service discovery wizard.)
Skip BiDi Transformation String   Controls invocation of bi-di transformation. Acceptable values: true or false. A blank value invokes the lookup mechanism.
Skip BiDi Transformation for Password String   Controls invocation of bi-di transformation for the Password property. Acceptable values: true or false. A blank value invokes the lookup mechanism.
Skip BiDi Transformation for Username String   Controls invocation of bi-di transformation for Username property. Acceptable values: true or false. A blank value invokes the lookup mechanism.

SystemNumber

Integer No System number of the application server. The value is a two-digit number, often 00. The default is 00.

Username

String Yes Name of the adapter’s user account on the SAP system. If bidirectional language support is enabled, this property is affected by the following BiDi properties, which are set using the enterprise service discovery wizard:
  • User Name BiDi Format: Controls the bi-di format for this property.
  • Skip BiDi Transformation for User Name: Controls invocation of bi-di transformation for this property.
Username BiDi Format String   Specifies the bi-di format for the Username property.
Related tasks
Configuring properties
Installing the application

Terms of use |

Last updated: Sun Mar 12 11:15:16 2006

(c) Copyright IBM Corporation 2005.
This information center is powered by Eclipse technology (http://www.eclipse.org)