converting legacy db components to BizTalk

Hello,

If you’re after a quick win, I would suggest wrapping your legacy components in a web-service and calling them via the SOAP adapter. Some further thoughts are below.

Cheers, Nick.

[quote user="Anonymous"]

I have some legacy database components that update database, and now need to add this code to BizTalk. What would be good way to proceed –

1.Call the legacy db components directly from BizTalk orchestration?

[nickh] Probably not the best option even if you did have the time to do the development – unless you can afford to wrap each db call in an atomic scope and take the performance hit in the orchestration, you’re potentially opening yourself up to a can of worms – i.e. you lose the robustness provided by the messaging engine, retries etc.

2.Wrap legacy db components in webservices and call webservices from BizTalk orchestration?

[nickh] Probably your best option – quick and you’ll get the ‘robustness’ of the messaging engine handling the SOAP calls.

3.Split & rewrite db calls directly from orchestrations using SQL adapter (I guess this might be most efficient but seem longest path)

[nickh] Yes, most efficient, however if you’re after a quick win, this is probably the slowest option. Maybe do a combination of this and WS, moving your heavy SQL processing tasks to the SQL adapter and more light-weight tasks to WS’s.

I would like to keep conversion effort low, but don’t want to compromise performance ..  any advice/suggestion is appreciated. 

[/quote]