Thanks for your reply..it really helped !!

My orchestration sends 5 different files to different locations based on routing rules using decide shape.

Now I need to batch files of same location as single message using sequential pattern.How to bind orchestration to receive frm 5 different locations and to batch files from a location together separated frm other location

Hi..You mean 5 different batching orchestration? Its not good practise-You guys are expert - why can't we achieve thro' generic orchestration for achieving this batching from 4 different locations?

Who said its not good practise. Keeping code simple , managebale is good practise.

Ofcourse u can do it in one orch. But in orch u will have to have different condiftions and loops for each batching anyway which would make things not neat. Keeping it separate keeps it clean.

Ur one port will have 5 rcv locations.

Ur genric will be bound to the port and follow the messages coming to the port via different locations. In orch have a check on the location from where its coming and start grouping the relevant messages.

Hi,

You can use Seqential Convoy to Receive the Messages and once all the messages are in you can combine them and create a new message to send the message.

I cannot see any issues with creating different processes for different locations as suggested by Pi_xel_xar. The best practice is to keep logic simple as long as you have too many process.

Please indicate "Mark as Answer" or "Mark as Helpful" if this post has answered the question

Rahul

HI ,

Thanks for your reply..

  The process would be that I would map each one of MESSAGE to the correct XML output and then store them in a folder (probably 1 folder for each buyerID of incoming file).  Every 10 minutes, those files would then be batched together into one single XML file ..

So the batching will be done a sequential convoy orchestration and since its messages coming from 4 different folders This will require 4 batching orchestration..Is this what you  are trying to say 'code will be manageable inspite of too many processes'..Please suggest !!

Hi,

have you tried using correlation here . If you have multiple receive location you can always build a correlation based on the receive port name (one receive port having multiple receive location)  and use multipart message to contract a aggregator message  or you can use Pipeline call to aggregrate .

You can refer below MSDN articles

https://msdn.microsoft.com/en-us/library/aa995576.aspx?f=255&MSPPError=-2147217396

http://social.technet.microsoft.com/wiki/contents/articles/29134.working-with-xlangmessage-inside-orchestration.aspx

Thanks

Abhishek

Hi,

There are 2 options for you for you:

• Create different orchestrations for different flows (different receive locations) and keep the process simplet and straight forward.
• Create a single orchestration which can have parallel processing and each branch would perform its own operation of getting all the files (sequential Convoy) and then aggregating them in a single message and send it.

Rahul

• Marked as answer by Joshlyn 21 hours 38 minutes ago

Hi,

There are 2 options for you for you:

• Create different orchestrations for different flows (different receive locations) and keep the process simplet and straight forward.
• Create a single orchestration which can have parallel processing and each branch would perform its own operation of getting all the files (sequential Convoy) and then aggregating them in a single message and send it.

Rahul

• Marked as answer by Joshlyn Monday, August 24, 2015 9:25 AM

Hi,

There are 2 options for you for you:

• Create different orchestrations for different flows (different receive locations) and keep the process simplet and straight forward.
• Create a single orchestration which can have parallel processing and each branch would perform its own operation of getting all the files (sequential Convoy) and then aggregating them in a single message and send it.

Rahul

• Marked as answer by Joshlyn Monday, August 24, 2015 9:25 AM

Hi,

There are 2 options for you for you:

• Create different orchestrations for different flows (different receive locations) and keep the process simplet and straight forward.
• Create a single orchestration which can have parallel processing and each branch would perform its own operation of getting all the files (sequential Convoy) and then aggregating them in a single message and send it.

Rahul

• Marked as answer by Joshlyn Monday, August 24, 2015 9:25 AM