The J2C activation specification properties (also referred to as message endpoint properties) correspond to the ActivationSpec interface of the J2EE Connector Architecture Specification. An activation specification is a JavaBean used during endpoint activation. Endpoint activation is the process of notifying the adapter of eligible listener threads.
J2C activation specification properties
Property | Type | Globalized | Description |
---|---|---|---|
Integer | No | Specifies the status code for dispatch failure. You must specify a value for this property (68 or 58) to cause the adapter to update the SAP failure status code after the adapter has retrieved an IDoc object for event processing. SAP converts this value to 40. | |
String | Yes | Specifies the descriptive text for dispatch failure. Specifying a value for this property is optional, even when you set AleUpdateStatus to true. | |
String | No | Specifies which IDoc Type and MessageType combinations are to be updated when the adapter is configured to update a standard SAP status code. You can define values for this property only if AleUpdateStatus has been set to true. The syntax for this property is: IDocType: MessageType [;IDocType: MessageType [;...]] where a semicolon (;) delimiter separates each IDoc Type and MessageType, and a comma (,) delimiter separates entries in a set. The following example illustrates two sets. In the example, MATMAS03 and DEBMAS03 are the IDocs, and MATMAS and DEBMAS are the message types: MATMAS03/MATMAS,DEBMAS03/DEBMAS. | |
Integer | No | If required, specifies the message code to use when the adapter posts the ALEAUD Message IDoc (ALEAUD01). Configure this message code in the receiving Partner Profile. You can set a value for this property only if AleUpdateStatus has been set to true. | |
Integer | No | Specifies the success status code for Application Document Posted. You must specify a value for this property (52 or 53) to cause the adapter to update the SAP success status code after the interface has retrieved an IDoc object for event processing. SAP converts this value to status 41 (Application Document Created in Receiving System). | |
String | Yes | Specifies the descriptive text for successful Application Document Posted. Specifying a value for this property is optional, even when you set AleUpdateStatus to true | |
boolean | No | Specifies whether an audit trail is required for all message types. This property must be set to true to cause the adapter to update a standard SAP status code after the adapter has retrieved an IDoc object for event processing. | |
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. | |
boolean | No | Indicates whether the adapter should create the event recovery table automatically if it doesn’t already exist. The default value is true. | |
String | Namespace for the business object definitions to be used by this adapter. This value should be taken from the user-provided value during the metadata discovery process. | ||
Integer | No | SAP Client number under which the adapter logs in, often 100. | |
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. | |
EDT BiDi Format | String | Controls the BiDi format specific for all EDT properties. | |
String | No | Name of event recovery database. If bidirectional language
support is enabled, this property is affected by the following bi-di properties,
which are set using the enterprise service discovery wizard: |
|
String | No | Name of the XA database driver used to connect to the Event Recovery Table for inbound events. Example: com.ibm.db2j.jdbc. DB2jXADataSource (for Cloudscape™). | |
String | No | Schema used for auto-creating the event recovery database.
If bidirectional language support is enabled, this property is affected by
the following bi-di properties, which are set using the enterprise service
discovery wizard: |
|
String | No | Name of event recovery table. If bidirectional language
support is enabled, this property is affected by the following bi-di properties,
which are set using the enterprise service discovery wizard: |
|
EDTURL | String | No | The URL to the EDT database. If bidirectional language
support is enabled, this property is affected by the following bi-di properties,
which are set using the enterprise service discovery wizard: |
EDT URL BiDi Special Format | String | Specifies the category of cases subject to special treatment during invocation of bi-di transformation to ensure accurate transformation of the category. | |
String | Yes | User name for connecting to the database. If bidirectional
language support is enabled, this property is affected by the following bi-di
properties, which are set using the enterprise service discovery wizard: |
|
String | Yes | User password for connecting to the database. If bidirectional
language support is enabled, this property is affected by the following bi-di
properties, which are set using the enterprise service discovery wizard: |
|
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 | Specifies the 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. | |
String | Yes | SAP Gateway Host where the gateway service is running. | |
String | No | Gateway server identifier; often sapgw00. 00 is the system number of the server running the SAP Gateway (usually an application server). May not be 00 if you have more than one server. The default is sapgw00. | |
String | No | When configuring the adapter for load balancing, specifies the name of the logon group that represents a group of application servers. | |
boolean | No | If the adapter encounters an error while processing the IDoc packet, it can behave in two different ways depending upon the IgnoreIDocPacket Errors configuration property. When this property is set to false, the adapter stops processing further IDocs in that packet and reports an error to the SAP system. When this property is set to true, the adapter logs an error and continues processing the rest of the IDocs in that packet. | |
String | No | Language in which the adapter logs in. The default is E, for English. | |
String | Yes | When configuring the adapter for load balancing, specifies the name of the message server. | |
Integer | Specifies the number of listener threads that are created when the adapter is initialized. A listener thread can handle one request at a time. Each listener thread handles a single event at a time. If you have multiple listener threads, the adapter can handle multiple events concurrently. The default is 1. It is recommended that you have no more listener threads than the available work processes in SAP. | ||
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 bi-di properties,
which are set using the enterprise service discovery wizard: |
|
String | Yes | Program identifier that the RFC Server program registers under. | |
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 value is false. |
Integer | No | When configuring the adapter for load balancing, specifies the logical name of the SAP system, also known as R3name. | |
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 EDT | String | Controls invocation of bi-di transformation for EDT properties. Acceptable values: true or false. A blank value invokes the lookup mechanism. | |
Skip BiDi Transformation for EDT URL | String | Controls invocation of bi-di transformation for EDT URL. Acceptable values: true or false. A blank value invokes the lookup mechanism. | |
boolean | No | Indicates whether or not the adapter needs to send the entire IDoc packet or split it into multiple IDocs. | |
String | No | System number of the application server. The value is a two-digit number, often 00. The default value is 00. | |
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 bi-di properties, which are set
using the enterprise service discovery wizard: |
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)