Queuing Biztalk Subscriptions -
Queuing Biztalk Subscriptions -
we have scheme sending hl7 messages biztalk using mllp hl7 accelerator. have several destination systems, need own format of hl7 message, utilize orchestrations each destination, each involving different transform. each orchestrationi uses filter subscribe receive port. subscription model works well, if need stop or undeploy 1 of orchestrations. drawback of subscription model, on force model there no queuing built in, if orchestration removed, messages picked receive port not queue system. or concern? how handle upgrades orchestration, etc. there improve design pattern?
a improve design in sentiment place transformations (maps) straight on send ports. can have filters on different send ports route destinations systems.
this design create updates bit easier there isn't orchestration first needs removed deploy new version of map. have stop port ( leaves subscription active , messages queued subscribing ports). after port stopped can modify resource (assembly) new version of map , start port start transforming , sending queued messages.
it's usally thought only utilize orchestration when need controll more complex workflow - not apply map in case.
biztalk
Comments
Post a Comment