Hi,

I have a simple scenario where I want to call two separate .Net functions,
each of which update a row in a table.

Orchestration:

Receive PO
|
Expression Update SQL Via .Net Method call
|
Expression Update SQL Via another .Net Method call
|
Stop

I have wrap them both in a Acid scope so if the last update fails the first
update is automatically rolled back. It is not currently working

I am not should how to go about doing this I Biztalk 2006. I have added
Enterprise component services to the .Net class doing the updates.

Can anyone point me to an example/sample that does something similar?

Thanks in advance,

Simon

[ Post a follow-up to this message ]

Hi Simon,

In order for .net code to participate in the atomic transaction, it needs to
be transaction enabled. You can create enterprise components in .net to do
this, (there may also be some new functionality in .net 2.0).

A simpler option may be to move the transaction logig into one stored
procedure, then make one call from your net code.

Regards,

Alan

--
The Bloggers Guide to BizTalk
http://geekswithblogs.com/asmith



"ee@ee.demon.co.uk" wrote:

> Hi,
>
> I have a simple scenario where I want to call two separate .Net functions,
> each of which update a row in a table.
>
> Orchestration:
>
> 	Receive PO
> 	        |
> 	Expression Update SQL Via .Net Method call
>  	        |
> 	Expression Update SQL Via another .Net Method call
> 	        |
> 	   Stop
>
> I have wrap them both in a Acid scope so if the last update fails the firs
t
> update is automatically rolled back. It is not currently working
>
> I am not should how to go about doing this I Biztalk 2006. I have added
> Enterprise component services to the .Net class doing the updates.
>
> Can anyone point me to an example/sample that does something similar?
>
> Thanks in advance,
>
> Simon
>

[ Post a follow-up to this message ]

Hi,

Thank you for taking the time to respond.

The problem with putting it into a store procedure is that all of the
visablity of the process is lost, i.e. I might as well use DTS!

Surly someone in this news group knows the best way of handing multiple DB
updates from within .net components that are being called from a Biztalk
orchestration?

Do people using Biztalk not generally have to worry about transaction based
updates?

Regards,

Simon

[ Post a follow-up to this message ]

try using compensation....

read this article

http://www.codeproject.com/useritem...ompensation.asp

"ee@ee.demon.co.uk" wrote:

> Hi,
>
> Thank you for taking the time to respond.
>
> The problem with putting it into a store procedure is that all of the
> visablity of the process is lost, i.e. I might as well use DTS!
>
> Surly someone in this news group knows the best way of handing multiple DB
> updates from within .net components that are being called from a Biztalk
> orchestration?
>
> Do people using Biztalk not generally have to worry about transaction base
d
> updates?
>
> Regards,
>
> Simon
>

[ Post a follow-up to this message ]

Thanks mate

My example is short running though, just like a DTS package. Is there an
example where two separate DB records are updated from within two separate
.Net component call from an orchestration with acid scope that are then
rolled back?

E.g.

Orchestration:

Receive PO
|
Expression Update SQL Via .Net Method call
|
Expression Update SQL Via another .Net Method call
|
Stop

Thanks in advance,

Jim

[ Post a follow-up to this message ]

> My example is short running though, just like a DTS package. Is there an
> example where two separate DB records are updated from within two separate
> .Net component call from an orchestration with acid scope that are then
> rolled back?

You need to make the .Net components Serviced Components (COM+).  By doing
this, they will take part in the same atomic transaction.

[ Post a follow-up to this message ]