文档下载 文档下载导航
设为首页 | 加入收藏
搜索 请输入内容:  
 导航当前位置: 文档下载 > 所有分类 > Interoperable transactions for e-business
侵权投诉

Interoperable transactions for e-business

For enterprise systems to interoperate, as in an e-business transaction, some kind of transaction management is crucial. Current standard transaction protocols do not meet the requirements for e-business transactions. In this paper, a new transaction model

The principal difference between database and e-business transactions is based on the resource behavior. For a database transaction, a resource is an entry in a database system (passive entity) and the owner is reactive only. For business transactions the resources are dynamic and owners are active agents that can decide whether and how they will execute a certain request. In complex scenarios, there might be even a negotiation about the behavior of the locked resource (e.g. rules on unlock and self-unlock) before lock application is attempted.

2.2 Current standards

The most significant recent developments on e-business transactions include BTP, BPEL, and WS-CAF that we discuss briefly.

BTP [BTP2002] – represents e-business execution as a nested transaction governed by two-phase outcome protocol. The protocol performs outcome determination; each sub-transaction has provisional and final effects. Lock-alike behavior is achieved through confirmations of effects. However, achieving of provisional effect already requires performing of some activity, and, in case it can’t complete successfully, compensation is necessary. All reservations are performed as part of the execution: a notion of resource capability verification is absent due to an optimistic bias towards participants’ functionality.

BPEL (WS-T [WST2002]) - has two major advantages: extensibility and a well-developed flow control language. Transaction aspects are addressed in WS-T as part of the protocol, separately covering atomic transactions and business agreements. Transaction properties of the former are ACID while the emphasis of business agreements is on outcome determination avoiding the notion of locks.

WS-CAF (WS-TXM [WSTXM2003]) is a recently proposed specification, addressing transactions. While a notion of preparation is introduced as a mechanism to determine participants’ readiness, it isn’t explicitly bound to context-derived obligations. The notion of locking is vague due to the fact that the protocol draws on context-based coordination and outcome determination as operational mechanisms.

Roughly speaking, we can say that the current standards do support typical advanced transaction solutions, in a flexible way,, but do not meet the requirements imposed by e-business transactions. Sometimes this is an intentional choice. However, the consequence is that the e-business transaction logic is now to be hidden in the application code or process models, which is not desirable.

2.3 E-business transaction model

In order to cope with the requirements above, e-business transactions should be modified compared to those of ATM. Transaction, following common business rationale, is divided into three phases (Figure 1). Each phase includes certain common business steps that lead to achievement of a business goal.. Issues of transaction goal determination, establishing business criteria, composition, etc. precede transaction execution and are beyond the scope of the proposed model. Similarly, performance analysis, functionality adjustment etc. are also not a part of a transaction.

The first phase is a transaction execution preparation or pre-transaction. It is split into two sub-phases: prepare and locking [Little2003]. Prepare is a verification (confirmation) of prospective participants’ functionality while locking indicates agreement of a Web Service to participate is a transaction. Technically, both prepare (check) and e-business locking are (a)synchronous message exchanges between prospective participants and a change of Provider’s state (and a context). Each step is followed by verification – checking if a transaction can be executed with available participants functionality. A phase (or each step) could be followed by saving context, which could be retrieved later or even used for another transaction.

上一页第3页

你可能喜欢

热门文档

相关文档

站点地图 | 文档上传 | 侵权投诉 | 手机版
本站所有资源均来自互联网,本站只负责收集和整理,均不承担任何法律责任,如有侵权等其它行为请联系我们.
文档下载 Copyright 2013 doc.guandang.net All Rights Reserved.  -  email