Business Objects / COM+ / MTS

I have a general question on how to implement transactions across multiple
web services using Microsoft and .Net.

Example: I have two webservices (both are simplified for sake of example).

1. wsUpdateChecking(amount) - this webservice will update the amount of
money in your checking account.
2. wsUpdateSavings(amount) - this webservice will update the amount of money
in your savings account.

The requirement is for a client (webservice consumer) to take $10 from
checking and put that $10 into savings. Given the current design, this
would require a call to wsUpdateChecking and a call to wsUpdateSavings. If
either call failed, the entire transaction should be rolled back.

My questions are:
1. Given the requirements and the 2 webservices, how would this transaction
be accomplished? Does COM+ / MTS offer the ability to manage both these
objects transactionally when they are two distinct, seperate services?

.....or would the correct solution involve creating a third webservice that
would call wsUpdateChecking & wsUpdateSavings to manage the transaction?

Any help is appreciated.




.

Relevant Pages

  • Re: Business Objects / COM+ / MTS
    ... could be two seperate assemblies made available through .net remoting. ... CF> multiple web services using Microsoft and .Net. ... wsUpdateChecking- this webservice will update the amount ... If either call failed, the entire transaction ...
    (microsoft.public.dotnet.distributed_apps)
  • RE: how to use Begintransaction ?
    ... If you are using web services and want transactional data, ... it> makes a call to myService - a webservice - passing in a serialized objDay>. ... Problem is if 1 of the 7 days fails to write, there's no> rollback functionality. ... But my transaction object exists only in the webservice, and that> webservice is killed and recalled every day of the 7 days of the week. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Business Objects / COM+ / MTS
    ... CF> I have a general question on how to implement transactions across ... wsUpdateChecking- this webservice will update the amount ... this would require a call to wsUpdateChecking and a call to ... If either call failed, the entire transaction ...
    (microsoft.public.dotnet.distributed_apps)
  • Re: Transactional webservice
    ... ph is basically a connection to my webservice. ... I could do it as an atomic transaction, but I am not sure how to transmit ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Business Objects / COM+ / MTS
    ... Assuming that your transaction only involves database transactions (and not ... MSMQ transactions for instance) it doesn't really matter how many assemblies ... wsUpdateChecking- this webservice will update the amount ... this would require a call to wsUpdateChecking and a call to ...
    (microsoft.public.dotnet.distributed_apps)