ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General Discussion » Consume messages by multiple apps: how to design

Post new topic  Reply to topic Goto page Previous  1, 2, 3
 Consume messages by multiple apps: how to design « View previous topic :: View next topic » 
Author Message
walterA
PostPosted: Sun Dec 27, 2015 6:38 pm    Post subject: Reply with quote

Novice

Joined: 22 Sep 2015
Posts: 20

bruce2359 wrote:
walterA wrote:

In my cases ... it will always publish message to the root.

Why? What is your purpose of publishing to the topic root - rather than publishing to apples, if the pub is about apples?



The problem is that the messages will be sent by the external application/vendor which is connected remotely (through message channel). It doesn't know to which internal topic to publish the message. The idea is to use an alias Q mapped to a topic. All messages will be published to the alias Q and will flow to the topic (at root level) - that's why all the messages will be published at the root level. I apologize that I was not able to explain this correctly.
Back to top
View user's profile Send private message
bruce2359
PostPosted: Sun Dec 27, 2015 11:08 pm    Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 9394
Location: US: west coast, almost. Otherwise, enroute.

walterA wrote:
All messages will be published to the alias Q and will flow to the topic (at root level) - that's why all the messages will be published at the root level. I apologize that I was not able to explain this correctly.

Why must the alias point to the root? Why can't the alias point to a real local queue?

Perhaps it would help you to think of a topic node as a queue.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live.
Back to top
View user's profile Send private message
walterA
PostPosted: Mon Dec 28, 2015 5:46 pm    Post subject: Reply with quote

Novice

Joined: 22 Sep 2015
Posts: 20

bruce2359 wrote:

Why must the alias point to the root? Why can't the alias point to a real local queue?



There will be only one (MQA) channel with the external system/vendor. And the vendor only knows about one (remote) queue to which it will be placing messages of different types. This remote (alias) queue will be mapped to the topic.

Another approach will be to have a distributed pub/sub system. In this case the external system will be publishing messages to the topic (at different levels) through MQA channel. While all subscriptions will be located remotely on recipient side. It sounds to me a bit complicated, because it requires additional efforts on the vendor side (which might be pretty complicated)
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Mon Dec 28, 2015 6:18 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY

you could also create an app that reads from the local queue and determines what the type of the message is, and then publish to the corresponding topic...
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
walterA
PostPosted: Sun Jan 31, 2016 10:17 am    Post subject: Reply with quote

Novice

Joined: 22 Sep 2015
Posts: 20

Thank you for all your comments! it is very helpful.

Most probable I will go with AiasQ mapped to a Topic. But will do a prototype first to analyze it more.

Is there any way to make sure that this system will not choke?

I understand how to analyze system load based on enqueue dequeue rate and max queue size for a simple topology. But in case of aliasQ mapped to Topic - I dont know even how to approach it. Any ideas? Anything that I can read on this?


Thanks agian
Back to top
View user's profile Send private message
bruce2359
PostPosted: Sun Jan 31, 2016 1:51 pm    Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 9394
Location: US: west coast, almost. Otherwise, enroute.

There will be no discernible difference. An alias is merely a pointer, and quickly resolved by MQ internals as is done fo QRemote definitions that resolve to a QLocal xmitq.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Sun Jan 31, 2016 10:04 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY

Depending on topology and cluster publishing, there may be a serious impact on cluster traffic. This has been regulated in version 8 with the use of a new type of qmgr/Topic specifically acting as publish and subscribing point for the cluster traffic.
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2, 3 Page 3 of 3

MQSeries.net Forum Index » General Discussion » Consume messages by multiple apps: how to design
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.