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.
Interoperable transactio... 暂无评价 6页 免费 Business_Models_for_Inte...... CONTRACT-BASED INTEROPERABILITY FOR E- BUSINESS TRANSACTIONS Abstract. Due to...
Land information system An interoperable framework for high resolution land ...IEEE Transactions on Parallel and Distributed Systems 14 (9), 897e908. ...
each business object executes transactions on one domain system and all of ...INTEROPERABLE MIDDLEWARE FOR COOPERATIVE APPLICATIONS AVAILABILITY 9 ? Recovery ...
It is the largest publisher of XML-based content for interoperable enterprise... to define properties for products, partners, and business transactions. ...
TIBCO is the Originator and Leader of Business ...All TIBCO solutions are interoperable and ...Direct access to mainframe transactions ? Only ...
accuracy to ENSURE BUSINESS CONTINUITY by forwarding legitimate transactions ?...Interoperable for mixed deployments. DDoS Mitigation Cisco Guard XT 5650 Cisco...
BUSINESS TRANSACTIONS... 268页 免费 3 - Open Standards and O... 22页...Interoperable standards Reliable, fixed terms of availability Strategies for ...
accuracy to ENSURE BUSINESS CONTINUITY by forwarding legitimate transactions ?...Interoperable for mixed deployments. DDoS Mitigation Cisco Guard XT 5650 Cisco...
(SME) to carry out a large subset of its business transactions with other...for really interoperable, applicationto-application interconnected transactional ...
transactions 90% (或1,200项服务)适合电子化的...interoperable standards 提供共用基建服务 Provision ...business and implementation plans for clusters ...
热门文档