Hello guys, Am working with an orchestration, which acceses a servicedcomponent class. I have to fix a bug in it. I need to know the reason for why they are using a servicedcomponent inside an orchestration?
One very useful case to use a ServicedComponent from an orchestration is to ensure transactional calls. If the component is marked as supporting transactions, and it is called from an atomic transaction scope in the orchestration, biztalk will make the scope into a DTC transaction and run the .NET component inside that same transaction.
Maybe that is what they are doing. Or maybe they depend on a different COM+ service. Maybe they are doing it just so they can execute it inside a Server COM+ application running under a particular identity (i.e. for security reasons) and so on.
As Stephen says, you’d need to ask whoever created it; I just wanted to point out that there are perfectly good reasons for using EnterpriseServices.
Viewing 1 reply thread
The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.