Section 11.5. Summary


11.5. Summary

Transactions are one of the most fundamental concepts in a Web services environment to ensure reliable application processing. However, support for transactions in the Web services world does require more flexible and extensible mechanisms for controlling application outcome than those typically offered by traditional distributed and database transaction models.

The Web services transaction specifications described in this chapter provide an extensible framework for coordinating and orchestrating application outcome by defining specifications for services that provide for the creation of computational activities, their registration with an outcome coordinator, and controlling the disposition of the actions taken by the activities. The generalized framework offers the capability to specify the operational context of a request (or series of requests), controlling the duration of the activity and defining the participants that need to be engaged in an outcome decision.

In addition, specific patterns (transactions) that are typically used within the industry for coordinating the outcome of differing application styles are defined:

  • WS Atomic Transactions Application operations on Web services occur completely or not at all, and results are not available until the transaction is complete.

  • WS Business Activity Application operations on Web services exhibit a loose unit of work, in which results are shared prior to completion of the overall activity. Each participant undoes the operations it has performed within the conversation.

The Web service transaction specifications provide a flexible approach to handling outcome processing. This approach ranges from existing classic transaction patterns to more general business process.

Web service transactions augment existing application environments by providing the mechanisms that allow Web services to work together and offer a reliable computing environment. The facilities in Web service transactions address the common failures that might occur and ensure that the Web Service application achieves an agreed outcome.



    Web Services Platform Architecture(c) SOAP, WSDL, WS-Policy, WS-Addressing, WS-BP[.  .. ] More
    Web Services Platform Architecture(c) SOAP, WSDL, WS-Policy, WS-Addressing, WS-BP[. .. ] More
    ISBN: N/A
    EAN: N/A
    Year: 2005
    Pages: 176

    flylib.com © 2008-2017.
    If you may any questions please contact us: flylib@qtcs.net