CODEWITHSUNDEEP
biztalkbiztalk-2010biztalk-2009biztalk-2013
Abhishek Gahlout
Abhishek Gahlout

Reputation: 3462

Best approach to follow when source is same and destinations are different in biztalk

I am in a situation where I need to develop the integration mechanism using biztalk server between different systems.

One of the scenario is as follows:

There is a source system (lets say S1) which generates some files in a folder and I used to pick these files,apply some logic and send to the destination systems. There are three different destination systems (D1,D2,D3) which needs to process the same files generated by source system S1. There is some defined frequency for all the three destination systems , to process the input files (generated by S1). So what should be the best approach in this scenario.

I have some in mind which are as follows , Please suggest me the best one.

-> Make three different orchestrations for the three different destinations.

-> Make one orchestration and manage the logic in that only.

-> Implement ESB. Is ESB worth of use in this scenario ?

Please suggest.

Upvotes: 0

Views: 120

Answers (2)

Vikas Bhardwaj
Vikas Bhardwaj

Reputation: 1510

It really depends on the logic you need to apply on files for different destination, the question you will ask yourself are: - Do you really need orchestration to apply the logic, can this be done using Inbound/outbound maps only or in pipeline. - Is logic significantly different for each destination? If not a common processing of message should be done. - Do you need to do a extensible design i.e. Is there a need where you may need to add more destinations in future?

Based on your question details, it very difficult to come up with exact approach. As good as you can design the application which is easily maintainable and extendable, you should be fine with any approach. You should definitely look at ESB implementation for dynamic routing to different destinations.

Upvotes: 1

zurebe-pieter
zurebe-pieter

Reputation: 3266

What logic are you actually thinking about?

In the most simple scenario you would only have 1 receive port and location and 3 send ports. The send ports would subscribe (via the send port Filter) to the messages they need.

In order to do that, you would need to promote the necessary properties in your receive location (or orchestration, but that has a performance cost). It all depends on your logic, but probably you would be able to put most (if not all) logic in a BizTalk mapping.

Upvotes: 1

Related Questions