1. Business Transaction Management Software for Application Coordination All current ws-bpel usage scenarios want BTM…  EAN.UCC Simple-EB explicitly calls for 5 Business Transactions.  CPFR (Collaborative Planning, Forecasting and Replenishment) requires several EDI transactions.  Not full business transactions in the sense we are discussing here, but lack of transactional integrity was an issue in UCC-sponsored interoperability test  RosettaNet PIPs (Partner Interface Processes) are business transactions.

2. Business Transaction Management Software for Application Coordination Excerpt from Simple-EB… > Place Order Order [ACCEPTED] > Provide Despatch Advice > Request Payment Despatch Advice [RECEIVED] Order [FULFILLED] Payment [RECEIVED]

3. Business Transaction Management Software for Application Coordination Excerpt from Simple-EB… > Place Order Order [ACCEPTED] > Provide Despatch Advice > Request Payment Despatch Advice [RECEIVED] Order [FULFILLED] Payment [RECEIVED] Each of these are Business Transactions

4. Business Transaction Management Software for Application Coordination Excerpt from Simple-EB… > Place Order Order [ACCEPTED] > Provide Despatch Advice > Request Payment Despatch Advice [RECEIVED] Order [FULFILLED] Payment [RECEIVED] Each transaction changes the state of the order for both parties.

5. Business Transaction Management Software for Application Coordination Excerpt from Simple-EB… > Place Order Order [ACCEPTED] > Provide Despatch Advice > Request Payment Despatch Advice [RECEIVED] Order [FULFILLED] Payment [RECEIVED] An order is a legal contract… …every change to a contract requires agreement from both parties.

6. Business Transaction Management Software for Application Coordination Excerpt from Simple-EB… > Place Order Order [ACCEPTED] > Provide Despatch Advice > Request Payment Despatch Advice [RECEIVED] Order [FULFILLED] Payment [RECEIVED] Unilateral compensation is not an appropriate undo mechanism… …a separate canceling transaction is better.

7. Business Transaction Management Software for Application Coordination Other common usage scenarios that want BTM…  Any kind of economic exchange between trading partners  Any critical interaction between independent agents  Customer self-service  Many internal scenarios, e.g:  resource allocation  resource exchanges between peers  coordinated updates to multiple applications

8. Business Transaction Management Software for Application Coordination ws-choreography use cases that want BTM..  3.2.3 D-UC-003 - Travel agent  3.2.4 D-UC-004- Alternative paths based on business rules  (It's an order-to-cash cycle and requires at least 3 transactions.)  3.2.5 D-UC-005 - Exception Handling Across Domains of Control  3.2.7 D- UC-007 - Choreography Dependency  3.2.8 D- UC-008 - Quote Request  (especially if extended to accept quote and order quoted products)  3.2.10 D-UC-010 - Interconnection of Document Management Systems  (would be much better with transactions than reliable messaging)  3.2.11 D- UC-11 _ Supporting collaboration

9. Business Transaction Management Software for Application Coordination UN/CEFACT BCF Business Transactions…  Protocol very similar to RosettaNet  UN/CEFACT Modeling Methodology (UMM) used by EAN.UCC to define Simple-EB  Protocol mapped to OASIS BTP in: http://www.choreology.com/resources/2002-11-14.MultiParty.Business.Transactions.plus.appendix.pdf  UN/CEFACT: “ Agreed that this is a valid solution for a UMM implementation complementing the work we are doing within the BCP team.”

10. Business Transaction Management Software for Application Coordination Problems with order compensation…  Indeterminate closure:  A compensation can fire because of compensations or faults in surrounding scopes.  “pulling the rug out from under the order”  When are the trading partners really committed?  I.e. when is it safe to ship the goods?  Unilateral undo (compensation is not a business agreement protocol):  One party can invoke a compensation without redress from the counterparty...  …nor a way to undo a compensation gone wrong.  “No compensation for a compensation”.

11. Business Transaction Management Software for Application Coordination Transactions + Compensations…  Previous problems related to compensations without transactions.  Compensations within transactions are OK:  Transaction completion provides closure.  Compensations of transactions not OK:  To undo a transaction requires another transaction.

12. Business Transaction Management Software for Application Coordination Generalization…  Compensation was designed, and is appropriate, for internal workflow activities.  Business transactions are better for economic exchanges between trading partners.  Compensation within transaction = OK.