The adapter processes an IDoc packet as one unit of work if all
the IDocs in the packet are of the same IDoc type. All the IDocs in the IDoc
packet are part of one XA transaction to an endpoint. The event processing
is similar to a single IDoc with respect to the event recovery mechanism;
the IDoc packet is considered a single unit of work, so a failure registered
by the endpoint for any one IDoc causes the whole packet to fail. A failure
requires that all the IDocs in the IDoc packet be sent to the endpoint again.
The adapter processes an inbound event for a non-split packet
according to the following procedure:
- When the SAP system sends a transaction ID to the adapter, the adapter
checks the status of the event and takes one of the following actions:
- If this is a new event, the adapter stores an EVNTID (which corresponds
to the transaction ID) along with a status of 0 (Created)
in the event recovery table.
- If the event status is -1 (Rollback), the adapter updates
the status to CREATED.
- If the event status is 1 (Executed), the adapter returns
an indication of success to the SAP system.
- The SAP system sends the IDoc packet to the adapter, which parses the
IDoc packet, converts it to an array of IDoc objects, and stores it in memory.
- The adapter sends the business objects to the endpoint. The adapter can
deliver objects to endpoints that support transactions as well as to endpoints
that do not support transactions.
- If an exception occurs while the adapter is processing the event or if
the endpoint generates an exception, the event status is updated to -1 (Rollback).
- If no exception occurs, the SAP system performs the following tasks:
- It sends a COMMIT call to the adapter, and the event is updated to 1 (Executed).
- It sends a CONFIRM call to the adapter.
The adapter then deletes the records with a 1 (Executed)
status and logs a common event infrastructure (CEI) event that can be used
for tracking and auditing purposes.
Terms of use |
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)