| Author |
Message |
 Topic: Consume messages by multiple apps: how to design |
walterA
Replies: 36
Views: 27673
|
 Forum: General Discussion Posted: Sun Jan 31, 2016 10:17 am Subject: Consume messages by multiple apps: how to design |
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 th ... |
| Topic: Consume messages by multiple apps: how to design |
walterA
Replies: 36
Views: 27673
|
Forum: General Discussion Posted: Mon Dec 28, 2015 5:46 pm Subject: Consume messages by multiple apps: how to design |
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 o ... |
| Topic: Consume messages by multiple apps: how to design |
walterA
Replies: 36
Views: 27673
|
Forum: General Discussion Posted: Sun Dec 27, 2015 6:38 pm Subject: Consume messages by multiple apps: how to design |
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 p ... |
| Topic: Consume messages by multiple apps: how to design |
walterA
Replies: 36
Views: 27673
|
Forum: General Discussion Posted: Sat Dec 26, 2015 12:55 pm Subject: Consume messages by multiple apps: how to design |
Ok, I see.. thank you so much for the link to the presentations. I did read of them.
In my cases the publishing application will be sending messages to the alias Q that will be mapped to the topic, ... |
| Topic: Consume messages by multiple apps: how to design |
walterA
Replies: 36
Views: 27673
|
Forum: General Discussion Posted: Sat Dec 26, 2015 11:17 am Subject: Consume messages by multiple apps: how to design |
| what I am trying to say is that the external system will always publish messages to the alias Q associated with the root topic. But I want the internal consumers to be able to subscribe to specific ty ... |
| Topic: Consume messages by multiple apps: how to design |
walterA
Replies: 36
Views: 27673
|
Forum: General Discussion Posted: Sat Dec 26, 2015 10:34 am Subject: Consume messages by multiple apps: how to design |
Why have you not tried some of the suggestions? Then you could have found out for yourself how a pub/sub topic hierarchy works. You can do a simple test using JUST the MQ Explorer.
There is no bet ... |
| Topic: Consume messages by multiple apps: how to design |
walterA
Replies: 36
Views: 27673
|
Forum: General Discussion Posted: Fri Dec 25, 2015 7:24 pm Subject: Consume messages by multiple apps: how to design |
That's because if you have the right topic hierarchy you will have published to
harvest/fruit/apple and subscribed to harvest/fruit/#
Have fun 
But how message "apple" will ... |
| Topic: Consume messages by multiple apps: how to design |
walterA
Replies: 36
Views: 27673
|
Forum: General Discussion Posted: Fri Dec 25, 2015 4:20 pm Subject: Consume messages by multiple apps: how to design |
Can someone help me with this question in case of Alias Queue approach.
Imagine the external system publishes some messages. They will go to the alias Q then to the topic and then to subscribers. H ... |
| Topic: Consume messages by multiple apps: how to design |
walterA
Replies: 36
Views: 27673
|
Forum: General Discussion Posted: Fri Dec 18, 2015 8:23 pm Subject: Consume messages by multiple apps: how to design |
What do you think?
A couple of things. That you still haven't explained anything about your actual requirement or why you are trying to do it using pub/sub.
because there might be different ... |
| Topic: Consume messages by multiple apps: how to design |
walterA
Replies: 36
Views: 27673
|
Forum: General Discussion Posted: Thu Dec 17, 2015 8:05 pm Subject: Consume messages by multiple apps: how to design |
| But still as an option to alias Q and pub-sub I can implement a router that distributes/broadcasts messages to the destination queues. It can use a dynamic routing table to determine recipients. In th ... |
| Topic: Consume messages by multiple apps: how to design |
walterA
Replies: 36
Views: 27673
|
Forum: General Discussion Posted: Sat Dec 12, 2015 12:44 pm Subject: Consume messages by multiple apps: how to design |
Thank you so much for the answers! It is very helpful.
if I use durable subscriptions, do I need to use persistent messages in the local queues? I need to make sure that no messages will be lost.
... |
| Topic: Consume messages by multiple apps: how to design |
walterA
Replies: 36
Views: 27673
|
Forum: General Discussion Posted: Mon Dec 07, 2015 3:40 pm Subject: Consume messages by multiple apps: how to design |
An event is the same as a message
So the system will look like this?
System A (external)| Remote Q1/Q Manager 1
|
MQ Channel
|
Alias Q/ Q Manager 2 (internal)
|
Topic
| ... |
| Topic: Consume messages by multiple apps: how to design |
walterA
Replies: 36
Views: 27673
|
Forum: General Discussion Posted: Sun Dec 06, 2015 7:06 pm Subject: Consume messages by multiple apps: how to design |
Do you mean multiple consumers - each consuming one message - as a transaction?
Does the consumer app send a reply back to the producer app?
There are multiple applications within the company. T ... |
| Topic: How to load test delivery time? |
walterA
Replies: 10
Views: 29287
|
Forum: IBM MQ Performance Monitoring Posted: Sun Dec 06, 2015 11:28 am Subject: Re: How to load test delivery time? |
Thank you very much for you explanation!
I have got an idea! What if I add timestamp into the message header when a message is put into the remote Q of system A and then when I consume the message ... |
| Topic: Consume messages by multiple apps: how to design |
walterA
Replies: 36
Views: 27673
|
Forum: General Discussion Posted: Sun Dec 06, 2015 10:41 am Subject: Consume messages by multiple apps: how to design |
Hello, can someone help me with this.
I will have an external system that will be sending messages through MQ channel to be consumed by my company internal applications. So the design would look l ... |
