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.
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 ...
热门文档