Abstract | ||
---|---|---|
Executing composed Web services in a transactional way requires coordination. WS-Coordination is a specification that can be exploited in developing coordinators for various types of transactions, which are based on Web services. WS-AtomicTransaction and WS-BusinessActivity are protocols that use WS-Coordination to define coordination types for short running atomic transactions and long-duration business transactions. A drawback of these coordination protocols is that they only recover from semantic failures but not from communication and system failures. In order to avoid this disadvantage, we have exploited WS-Coordination in developing a coordinator, which also recovers from communication and system failures. This, however, requires that the coordinator as well as the participants of the protocol have to keep a log in a stable storage. In this paper, we present the protocol and illustrate its functionality by an example. |
Year | DOI | Venue |
---|---|---|
2009 | 10.1145/1806338.1806436 | iiWAS |
Keywords | Field | DocType |
composing web service,coordination protocol,stable storage,coordination type,various type,semantic failure,long-duration business transaction,system failure,atomic transaction,web service,ensuring recoverability,atomic transactions,orchestration,web services | Atomicity,Drawback,WS-Coordination,Computer science,Login,Web service,Orchestration (computing),Database,Disadvantage,Stable storage | Conference |
Citations | PageRank | References |
1 | 0.37 | 10 |
Authors | ||
1 |
Name | Order | Citations | PageRank |
---|---|---|---|
Juha Puustjärvi | 1 | 111 | 22.64 |