文档下载 文档下载导航
设为首页 | 加入收藏
搜索 请输入内容:  
 导航当前位置: 文档下载 > 所有分类 > 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

to un-fulfillment of post-transactional obligations which are results of transaction execution (e.g. warranties, maintenance, etc.). In essence it is a monitoring of contract clauses against failure for an extended (pre-defined) period of time. Global transaction is completed only when post-transaction monitoring is completed successfully.

The proposed model provides the following advantages:

- the proposed protocol is a contract-governed, while for other protocols business logic

is implemented in the execution flow;

- transaction separation into phases to address business and technical issues more

precisely;

- phases could be addressed by several protocols thus enabling flexibility;

- checking and locking are mechanisms to ensure correct execution through establishing obligation-based relationships between participants at pre-transaction

phase, eliminating uncertainty during execution (risk management) and eventually minimizing transaction cost (due to possible decrease in sub-transaction failures);

- post-transaction monitoring allows fulfillment of extended post transaction

obligations without it being part of the main transaction, thus enabling externalization of the transaction’s results as soon as they could be determined and used.

Although the distinction between a prepare and a locking step is made in several e-business transaction models, the exact meaning of “preparing” and “locking” is not always clear. For example, in their discussion of WS-Transaction, Alonso et al (2003) state that for web services it is “difficult to characterize the notion of resources, locks and rollback” (p.226). In this paper, we suggest the following characterization:

Prepare phase – at this phase we propose functionality verification of prospective participants. Being part of the pre-transaction, it precedes both locking and execution. Other preparatory mechanisms (protocol-specific) might involve application of holds, initialisations, soft locks, etc. We assume this phase’s activities verify functionality of prospective participants and don’t impose any definite reservation, neither they form an obligation (therefore, the terms lock and hold are misleading). In case of completion or execution failure the preparation doesn’t require compensation.

Because participant’s profile, initially published in a registry might reflect actual functionality incorrectly (being outdated) or incompletely (containing insufficient information to invoke provider’s functionality), the requesting party might want to check this information. Checking (or verification) is performed either at the provider itself (if it is trusted party) or at a third party.

While functionality restrictions are quite rigid, capacity restrictions vary due to resources’ utilization by other parties. Exact capacity value (or, rather, available capacity) is correct only at lock application, however, any estimate performed before invocation also contributes to the efficiency of the execution scenario because it allows excluding (potentially) unavailable participants from the scenario without the need of a lock.

Querying a registry is an optional part of the pre-transaction phase not to be confused with checking, typically preceding it. To perform a query a Requestor should know the location of the required registry and the API to manipulate it (or have its access brokered) and should have rights to access it. A Registry itself is of UDDI, ebXML or any other standard (supported type), is itself an independent entity, and is known before the transaction begins.

Locking Phase – some protocols employ explicit locking to ensure prospective participants’ enlistment. A lock creates obligations. This phase follows the prepare phase and assumes the existence of a contract or similar agreement specifying the type of locks to be applied and their characteristics. The lock type should be supported both by requesting party and by resource owners.

上一页第5页

你可能喜欢

热门文档

相关文档

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