Customers defined by Biztalk Client signed

Question

I am developing a Biztalk solution that requires client applications to sign and receive only a specific subset of event messages, depending on their user permissions. Subscription will be through routing by topic or content. The client will subscribe once and receive many messages until they unsubscribe.

Client requests will be displayed in the 100s, and signed topics can change on a regular basis, so identifying a separate Biztalk send port for each receiver is not a viable solution.

I thought that I could create an additional message broker service that supports individual client subscriptions and distributes messages sent from the biztalk port.

I also saw that the recipient list template can be built using orchestrations. It seems to me that I still adhere to the request-response template, although I am getting a one-way subscription message for many returned event messages.

The solution for my message broker seems to double the fact that Biztalk should be good, so I assume I don't have any important functionality. Has anyone tried such an application before and can give some pointers? Should I invest in an ESB toolkit as a solution? I looked on the net, but nothing makes it very clear for this type of topic subscription model.

Thanks Phil

Answer 1

Take a look at the ESB Toolkit. You can use the route functionality that it adds to BizTalk, either using one of the built-in converters (for example, UDDI), or using your own custom converter. This allows you to route messages based on configuration (stored in business rules or elsewhere).

You'll find a developer-oriented overview video of the ESB Toolkit on MSDN, which is a worthy introduction to the design and tooling process. There are also some useful videos.

, . Disasembler ESB Dispatembler, , .

:

• - SOAP, , , , ESB .
• Scatter-Gather - SOAP, , ESB on-ramp . - , , , . ServiceDispatcher .

" " , , ( ).