Sun Microsystems SAP BAPI manual Rollback Bapi

Chapter 3	Section 3.3
Setting SAP BAPI eWay Properties	eWay Connectivity Map Properties

Table 5 Outbound eWay—Client Connection Settings

Name	Description	Required Value
Transaction Mode	Specifies the transaction mode.	A transaction mode of Non-
		Transactional or Transactional
	Non-Transactional	RFC(tRFC), via VIA COMMIT/
		ROLLBACK BAPI.
	Actions performed by BAPI call are
	committed immediately and	The default mode is NON-
	automatically by SAP R/3 (auto commit). In	TRANSACTIONAL.
	this mode, use the execute() method in
	the OTD.
	Transactional RFC (tRFC)
	eWay communicates with SAP R/3 using
	unique transaction IDs (TID) to avoid
	message repeats. Use the
	executeAsynchronous(eid) method in the
	OTD in this mode.
	VIA COMMIT/ROLLBACK BAPI
	Performs a single phase commit, where
	actions performed by BAPI calls are
	committed or rolled back by calling
	BAPI_TRANSACTION_COMMIT or
	BAPI_TRANSACTION_ROLLBACK. In this
	mode you must use the commit and
	rollback methods on the BAPI/RFC OTD.
Transaction ID	Specifies the location of the Transaction	A valid path to the database
Verification	ID Verification database.	file.
Database
	Specify the name of the file-based	For example, the default
	database which persists the TIDs. Provide	location could be:
	the path to the database file that records
	the disposition of all transactions	C:\JavaCAPS\data\SapTRFC.TI
	outgoing from this eWay. The database	Ddb
	records whether transactions are:
	ƒ C (committed)
	ƒ U (unprocessed or rolled-back)
	ƒ R (reserved or pending)

eWay™ Adapter for SAP BAPI User’s Guide 29 Sun Microsystems, Inc.