05-17-05 12:47 PM
Hi Paul,
From my point of view, you needn't worry about the long-executing
because BizTalk is just designed for this kind of asynchronous
business processing scenarios. Just use a SOAP "solicit-response" to
send the request and wait for the response. Then the workflow will
become pending on the receive, which is still acceptable even if it's
a several days or weeks long process. So you can just think this is
an "asynchronously web service call" from client-side. However due to
the built-in performance tuning feature of BizTalk engine, the long
suspended orchestration instance may be moved out from memory and get
into "dehydrated" state. For this kind of cases, you need a prior
configured correlation set to let the message subscriber engine know
when a response message is finally received which dehydrated instance
has to be actived to process it.
For your reference, the following articles should highlight some
valuable points of this topic, especially the sections like:
"Compensation enables long-running transactions (LRTs) to be
managed..."
Build Better Business Processes with Web Services in BizTalk Server
2004
http://msdn.microsoft.com/msdnmag/i...WS/default.aspx
BizTalk Server 2004 Convoy Deep Dive
http://msdn.microsoft.com/library/d...ary/en-us/BTS_2
004WP/html/956fd4cb-aacc-43ee-99b6-f6137a5a2914.asp
Please update here if you have any further questions. Thanks.
Best regards,
WenJun Zhang
Microsoft Online Partner Support
This posting is provided "AS IS" with no warranties, and confers no
rights.
[ Post a follow-up to this message ]
|