IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Services and service-related functions > Access external services with adapters > Configure and using adapters > IBM WebSphere Adapters > SAP Software > SAP interfaces > BAPI interfaces > Inbound processing

Event recovery

You can configure the adapter for BAPI inbound processing so that it supports event recovery in case a failure occurs while the event is being delivered from the adapter to the endpoint. When event recovery is specified, the adapter persists the event state in an event recovery table that resides on a data source.

Event recovery is not the default; you must specify it by enabling once-only delivery of events during adapter configuration. You must also set up the data source before you can create the event recovery table.


Data source

Event recovery for BAPI inbound processing requires that a JDBC data source be configured. You use the administrative console to configure the data source. You select a JDBC provider (for example, Derby) and then create a new data source.


Event recovery table

You can create the event recovery table manually, or you can have the adapter create the event table. The value of the EP_CreateTable configuration property determines whether the event recovery table is created automatically. The default value of this property is True (create the table automatically).

To create the table manually, use the information provided in the following table:

Event recovery table fields
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 BAPI transactions specified in the application is observed. Event ordering is also affected by the number of event listeners. However, at some point all the BAPI transactions are transferred.

EVNTSTAT INTEGER Event processing status. Possible values are:

  • 0 (Created)
  • 1 (Executed)
  • 3 (In Progress)
  • -1 (Rollback)

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.

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 Not used for BAPI inbound processing.
BQPROC INTEGER Not used for BAPI inbound processing.
EVNTDATA VARCHAR(255) Not used.

Inbound processing for the BAPI interface