WebSphere Adapter for SAP Software
The adapter supports event recovery for ALE inbound processing in case of abrupt termination. During event processing, the adapter persists the event state in an event recovery table that resides on the data source. You must set up this data source before you can create the event recovery table.
ALE inbound scenarios require a JDBC data source to be configured. The data source is used for event tracking and recovery.
You set up the data source in the administrative console of WebSphere® Process Server or WebSphere Enterprise Service Bus. You select a JDBC provider (for example, Cloudscape™ 5.1) and then create a new data source.
Table field name | Type | Description |
---|---|---|
EVNTID | VARCHAR(255) | Transaction
ID for the tRFC (Transactional Remote Function Call) protocol. The tRFC protocol significantly improves the reliability of the data transfer, but it does not ensure that the order of ALE transactions specified in the application is observed. Event ordering is also affected by the number of event listeners. However, at some point all ALE transactions are transferred. |
EVNTSTAT | INTEGER | Event processing status. Possible values are:
|
XID | VARCHAR(255) | An
XA resource keeps track of transaction IDs (XIDs) in the event recovery table.
The adapter queries and updates that XID field. During recovery, WebSphere Application
Server calls the resource adapter, querying it for XA resources, and then
does transaction recovery on them. Note: The XA resource is used to enable
assured once delivery. Make sure the activation specification property Assured
Once Delivery is set to true.
|
BQTOTAL | INTEGER | Total number of IDocs in the packet. |
BQPROC | INTEGER | Sequence number of the IDoc in the packet that the adapter is currently processing. |
EVNTDATA | VARCHAR(255) | Not used. |
Configure a separate event recovery table for each endpoint. The same data source can be used to hold all of the event recovery tables.
Last updated: Mon 30 Oct 2006 03:34:55
(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)