Advances in WS-Transaction and WS-Coordination
-
Upload
raya-waters -
Category
Documents
-
view
17 -
download
1
description
Transcript of Advances in WS-Transaction and WS-Coordination
![Page 1: Advances in WS-Transaction and WS-Coordination](https://reader036.fdocuments.us/reader036/viewer/2022082818/56813006550346895d95776e/html5/thumbnails/1.jpg)
Advances inWS-Transaction and
WS-Coordination
William Cox, Ph.D.OASIS Symposium on Reliable Infrastructure
New Orleans
26 April 2004
![Page 2: Advances in WS-Transaction and WS-Coordination](https://reader036.fdocuments.us/reader036/viewer/2022082818/56813006550346895d95776e/html5/thumbnails/2.jpg)
Cox OASIS Symposium 20040426 2
Outline
• Motivation and History
• The Specifications
• Evolution
• Specification Techniques
• Comparisons
• Standardization Issues
• Future
• Summary and References
![Page 3: Advances in WS-Transaction and WS-Coordination](https://reader036.fdocuments.us/reader036/viewer/2022082818/56813006550346895d95776e/html5/thumbnails/3.jpg)
Cox OASIS Symposium 20040426 3
Disclaimer
• All opinions are those of the individual author of this presentation, and do not necessarily reflect those of the companies or individuals who are the specification authors.
• “My opinion, and welcome to it.”- apologies to James Thurber
![Page 4: Advances in WS-Transaction and WS-Coordination](https://reader036.fdocuments.us/reader036/viewer/2022082818/56813006550346895d95776e/html5/thumbnails/4.jpg)
Cox OASIS Symposium 20040426 4
Motivations
• Support Business process, legacy integration• Designed from the ground up as composable
Web services• Tailored to specific needs
– WS-AT – tightly coupled, legacy integration, rollback semantics
– WS-BA – loosely coupled, long running, compensation semantics
– WS-C – Factoring of context management
![Page 5: Advances in WS-Transaction and WS-Coordination](https://reader036.fdocuments.us/reader036/viewer/2022082818/56813006550346895d95776e/html5/thumbnails/5.jpg)
Cox OASIS Symposium 20040426 5
History
• XA (X/Open)
• OMG Object Transaction Service– And Extended Structures for OTS
• XOCP, others
• BTP (similar goals but more complex)
• WS-CAF (overlapped completion of v1.1)
![Page 6: Advances in WS-Transaction and WS-Coordination](https://reader036.fdocuments.us/reader036/viewer/2022082818/56813006550346895d95776e/html5/thumbnails/6.jpg)
Cox OASIS Symposium 20040426 6
Published Specifications
• August 2002 Publications– WS-Coordination 1.0– WS-Transaction 1.0 [WS-TX]
• September 2003 Publications– WS-Coordination 1.1 [WS-C]– WS-AtomicTransaction [WS-AT]
• January 2004 Publication– WS-BusinessActivity [WS-BA]
• Abbreviations– WS-Transaction [WS-TX] refers to WS-AT+WS-BA
![Page 7: Advances in WS-Transaction and WS-Coordination](https://reader036.fdocuments.us/reader036/viewer/2022082818/56813006550346895d95776e/html5/thumbnails/7.jpg)
Cox OASIS Symposium 20040426 7
Specification Relationships
WS-Transaction
WS-AtomicTransaction
WS-BusinessActivity
WS-Coordination
WS-Coordination
WS-Addressing
v1.0 v1.1
![Page 8: Advances in WS-Transaction and WS-Coordination](https://reader036.fdocuments.us/reader036/viewer/2022082818/56813006550346895d95776e/html5/thumbnails/8.jpg)
Cox OASIS Symposium 20040426 8
Structural Evolution v1.0-v1.1
• WS-AtomicTransaction and WS-BusinessActivity are now separate specifications– Were subparts of WS-TX 1.0
• Use of WS-Addressing Endpoint Reference’s opaque ReferenceProperties throughout
• Editorial and readability improvements
• Separate publication of WS-AT and WS-BA
![Page 9: Advances in WS-Transaction and WS-Coordination](https://reader036.fdocuments.us/reader036/viewer/2022082818/56813006550346895d95776e/html5/thumbnails/9.jpg)
Cox OASIS Symposium 20040426 9
Technical Evolution v1.0-v1.1
• General– Adopted opaque Endpoint Reference from WS-Addressing
• v1.0 “roll your own” contributed to WS-Addressing requirements
– Updated and enhanced security considerations, policy
• WS-AT– Renamed to Volatile 2PC, Durable 2PC– Complete state tables
• WS-BA– Named more consistently
• BusinessActivityWithCoordinatorCompletion• BusinessActivityWithParticipantCompletion
– Renamed some states– Complete state tables
![Page 10: Advances in WS-Transaction and WS-Coordination](https://reader036.fdocuments.us/reader036/viewer/2022082818/56813006550346895d95776e/html5/thumbnails/10.jpg)
Cox OASIS Symposium 20040426 10
Specification Techniques
• State reduction through simplification– Factored WS-Coordination– Didn’t try to view state of entire interaction
• Only the coordinator and participant separate views
• Some additional care for consistency designed in
– Acknowledge then ignore “state smear”
• Broad applicability for WS-Coordination– WS-AT, WS-BA, other coordinations
![Page 11: Advances in WS-Transaction and WS-Coordination](https://reader036.fdocuments.us/reader036/viewer/2022082818/56813006550346895d95776e/html5/thumbnails/11.jpg)
Cox OASIS Symposium 20040426 11
Some Comparisons
• WS-C/WS-TX– WS-Coordination specified as simple algorithm– WS-AT has 7 states– WS-BA has 8/9 states
• BTP has 28 Superior, 36 Inferior states– But includes ~ WS-C x WS-BA states in one
machine
![Page 12: Advances in WS-Transaction and WS-Coordination](https://reader036.fdocuments.us/reader036/viewer/2022082818/56813006550346895d95776e/html5/thumbnails/12.jpg)
Cox OASIS Symposium 20040426 12
Some Comparisons (continued)
• WS-CAF—Bookkeeping difficult– Builds on context mgt protocol WS-CTX, as
does WS-TX– Atomic has 8 states and 14 messages– LRA has many sub-protocols (total of 40
messages)
![Page 13: Advances in WS-Transaction and WS-Coordination](https://reader036.fdocuments.us/reader036/viewer/2022082818/56813006550346895d95776e/html5/thumbnails/13.jpg)
Cox OASIS Symposium 20040426 13
Another Comparison
• Pages of specification– BTP: 188 pages– WS-CAF base docs 240 pages– WS-Coordination+WS-AT+WS-BA 59 pages
• Does reflect time needed to read and understand
![Page 14: Advances in WS-Transaction and WS-Coordination](https://reader036.fdocuments.us/reader036/viewer/2022082818/56813006550346895d95776e/html5/thumbnails/14.jpg)
Cox OASIS Symposium 20040426 14
Standardization Issues
• Use of WS-Addressing requires standardization of at least Endpoint Reference– This is also an issue for the new WS-Resource Framework and
WS-Notification TC base documents
• Factoring useful if not overdone– WS-TX/WS-C factoring seems about right
• Specify, demonstrate interoperability, iterate– Focus on interoperable implementations important
– When and in which cycle?
– More mature specs into standardization process vs buy-in
![Page 15: Advances in WS-Transaction and WS-Coordination](https://reader036.fdocuments.us/reader036/viewer/2022082818/56813006550346895d95776e/html5/thumbnails/15.jpg)
Cox OASIS Symposium 20040426 15
The Future
• Author companies have committed to submitting to a standards organization
• Feedback meeting March 2004– See references
• Comment license required – So can maintain royalty-free approach to these specs
• Interoperability event in planning
![Page 16: Advances in WS-Transaction and WS-Coordination](https://reader036.fdocuments.us/reader036/viewer/2022082818/56813006550346895d95776e/html5/thumbnails/16.jpg)
Cox OASIS Symposium 20040426 16
Summary
• WS-Transaction and WS-Coordination simple enough, rich enough
• Composable web services target level
• Specifications at the right level– Reasonable number of states
– Reasonable number of protocols
– Comparatively lower complexity than competing specs
• Progressing to interoperability testing and submission to a standards organization
![Page 17: Advances in WS-Transaction and WS-Coordination](https://reader036.fdocuments.us/reader036/viewer/2022082818/56813006550346895d95776e/html5/thumbnails/17.jpg)
Cox OASIS Symposium 20040426 17
References
• WS-Coordination• WS-AtomicTransaction• WS-BusinessActivity• WS-Addressing• IBM Links
http://www-106.ibm.com/developerworks/views/webservices/standards.jsp
Alphabetization problems--some under “WS-”, some under “Web Services”
• Microsoft Linkshttp://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnglobspec/html/wsatspecindex.asp
• BEA Linkshttp://dev2dev.bea.com/technologies/webservices/standards.jsp
Interoperability and Feedbackhttp://www-106.ibm.com/developerworks/offers/WS-Specworkshops/ws-tx200402post.html
http://msdn.microsoft.com/webservices/community/workshops/transactionws032004.aspx
![Page 18: Advances in WS-Transaction and WS-Coordination](https://reader036.fdocuments.us/reader036/viewer/2022082818/56813006550346895d95776e/html5/thumbnails/18.jpg)
Cox OASIS Symposium 20040426 18
References (continued)
• WS-CAF (Arjuna, Fujitsu, Iona, Oracle, Sun) July 2003, OASIS TC
– http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ws-caf
• BTP OASIS TChttp://www.oasis-open.org/committees/tc_home.php?wg_abbrev=business-transaction
– BTP 1.0http://www.oasis-open.org/committees/download.php/1184/2002-06-03.BTP_cttee_spec_1.0.pdf
– BTP Primerhttp://www.oasis-open.org/committees/download.php/2077/BTP_Primer_v1.0.20020605.pdf