Enrutamiento/filtrado de mensajes sin orquestaciones

A lot of our use cases for Biztalk involve simply mapping and routing HL7 2.x messages from one system to another. Implementing maps and associating them to send/recieve ports is generally straightforward, but we also need to do some content based filtering on the sending side.

For example, we may want to only send ADT A04 and ADT A08 messages to system X if the sending facility is any 200 facilities (out of a possible 1000 facilities we have in our organization), but System Y needs ADT A04, A05, A8 for a totally different set of facilities and only for renal patients.

Because we're just routing messages and not really managing business processes here, utilzing orchestrations for the sole purpose to call out to the business rule engine is a little overkill here, especially considering that we'd probably need a seperate orchestration for each ADT type because of how schemas work. Is it possible to implement filter rules like this without using using orchestrations? The filters functionality of send ports looks a little too rudimentary for what we need, but at the same time I'd rather not develop and manage orchestrations.

preguntado el 26 de junio de 12 a las 16:06

I don't have BizTalk installed at the moment, but am confident you can do what you want without orchestrations, just using send port filtering. You can (I believe, it has been a while) call out to the bre from a receive port if needed (custom pipeline code but not too difficult) to get the right promoted properties into place. -

This blog post describes a somewhat similar scenario. It uses a custom pipeline component which calls the BRE and promotes properties to indicate target subscribers: blogs.msdn.com/b/paolos/archive/2011/06/01/… -

Or you can use a pre-rolled custom pipeline component. brepipelineframework.codeplex.com -

2 Respuestas

You might be able to do this with property schemas...

You need to create a property schema and include the properties (from the other schemas) that you want to use for routing. Once you deploy the schema, those properties will be available for use as a filter in the send port. Start from aquí, you should be able to find examples somewhere...

Respondido el 28 de junio de 12 a las 08:06

You are right, but what I found is that the filter functionality in the send port is so clunky to work with if you are dealing with a lot of filters. Additionally if you had a complex filter in mind "((this and this) or (this and this)) and this) you can't define that type of logic through the send port filter, to my knowledge. - Jeremy

This is how we do it. We don't have very complex filters though. - arrendajo

Not ideal, but complex filters could be achieved by assigning higher-level properties to the message in earlier processing. For example, rather than ((IsManager And IsFinance) or (IsAdmin and IsHR)) And IsActive, you could assign an IsActiveFinanceProcessor property using say a BRE receive pipeline. - mate mitchell

As others have suggested you can use a custom pipeline component to call the Business Rules Engine.

And rather then trying to create your own, there is already an open source one available called the BizTalk Business Rules Engine Pipeline Framework

By calling BRE from the pipeline you can create complex rules which then set simple context properties on which you can route your messages.

Full disclosure: I've worked with the author of that framework when we were both at the same company.

Respondido 22 Jul 16, 04:07

No es la respuesta que estás buscando? Examinar otras preguntas etiquetadas or haz tu propia pregunta.