Hi,

I am working on a BizTalk application that needs to communicate with other
systems using Websphere MQ. (I'm pretty new to MQ stuff.) I am trying to
decide if it's optimal to:

1 Use one inbound and one outbound message queue for each system, with all
the different messages transmitted on the some queue (needs 4 queues).

2 Use one queue for each message type for each system (needs about 20 queues
).

The first option requires less maintainance, but having all the
orchestrations connected to the same inboud queue will need a complex pub-su
b
architecture, (there are also file adapters in the system).

Has anyone worked with Websphere MQ (or MQ Series), and knows what the best
practice for this solution would be?

Any help would be great...

Regards,

Alan




--
BizTalk 101 - Back to Basics
BizTalk Patterns and Practices
http://geekswithblogs.com/asmith

[ Post a follow-up to this message ]

I think you are better off using fewer queues. If you suddenly have more
messages you have to add queues again, instead of only changing the
filtering in BizTalk. If you are talking about BizTalk 2004 and the upcoming
adapter, you can use it to read and write the MQ context properties and
filter on these values.

"Microsoft® BizTalk® Adapter for MQSeries provides a set of context
properties, specific to MQSeries, for use in your applications. You can use
these properties in filter expressions and in your orchestrations."

E.g.:
MQMD_MsgId

Best regards
Niklas E


"Alan Smith" <AlanSmith@discussions.microsoft.com> wrote in message
news:404C64E8-39DC-4B07-81A2-37B55EE090E8@microsoft.com...
> Hi,
>
> I am working on a BizTalk application that needs to communicate with other
> systems using Websphere MQ. (I'm pretty new to MQ stuff.) I am trying to
> decide if it's optimal to:
>
> 1 Use one inbound and one outbound message queue for each system, with all
> the different messages transmitted on the some queue (needs 4 queues).
>
> 2 Use one queue for each message type for each system (needs about 20
> queues).
>
> The first option requires less maintainance, but having all the
> orchestrations connected to the same inboud queue will need a complex
> pub-sub
> architecture, (there are also file adapters in the system).
>
> Has anyone worked with Websphere MQ (or MQ Series), and knows what the
> best
> practice for this solution would be?
>
> Any help would be great...
>
> Regards,
>
> Alan
>
>
>
>
> --
> BizTalk 101 - Back to Basics
> BizTalk Patterns and Practices
> http://geekswithblogs.com/asmith
>

[ Post a follow-up to this message ]