Author |
Message
|
kash3338 |
Posted: Fri Jan 01, 2016 7:39 am Post subject: Queue to Topic |
|
|
Shaman
Joined: 08 Feb 2009 Posts: 709 Location: Chennai, India
|
Hi,
Wish you all a Happy New Year 2016!
Is there is a way to change a Queue object to Topic seamlessly?
We have a Queue for which a service is already listening and there is a new requirement for another service to be built with the same message coming over that queue. If that Queue object can be changed to Topic, we have add one more subscriber for the new service. Is there any other better approach? |
|
Back to top |
|
 |
smdavies99 |
Posted: Fri Jan 01, 2016 8:22 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
An Alias Queue can be used to post to a topic. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
kash3338 |
Posted: Fri Jan 01, 2016 8:27 am Post subject: |
|
|
Shaman
Joined: 08 Feb 2009 Posts: 709 Location: Chennai, India
|
smdavies99 wrote: |
An Alias Queue can be used to post to a topic. |
Agreed. I thought about this option before raising it here. Even in that case, I need to change my existing service to replace the Alias Queue name in place of the actual Queue name configured currently.
I am in a position where I cannot change the service that's already running in Production. Hence any other option to get the same message for another service would be helpful. |
|
Back to top |
|
 |
PeterPotkay |
Posted: Fri Jan 01, 2016 8:40 am Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
You change the application that is putting to put to a new Alias Q name that resolves to a topic.
You build an administrative subscription for the existing listening service so messages continue to arrive on the existing local q for the existing service.
The existing service listening to the existing local q does not have to change.
Create new administrative subscriptions to new local queues for new services that needs these messages.
if you reply you can't change the putting application in any way as well, I would reply, you want to make changes to how your system behaves, but can't change anything? That does not compute. _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
kash3338 |
Posted: Fri Jan 01, 2016 8:51 am Post subject: |
|
|
Shaman
Joined: 08 Feb 2009 Posts: 709 Location: Chennai, India
|
PeterPotkay wrote: |
You change the application that is putting to put to a new Alias Q name that resolves to a topic.
You build an administrative subscription for the existing listening service so messages continue to arrive on the existing local q for the existing service.
The existing service listening to the existing local q does not have to change.
Create new administrative subscriptions to new local queues for new services that needs these messages. |
This is the solution that we currently have, but this still requires a "change"to the service that PUT's to the Queue. Without that, is there any other way out is my query here.
PeterPotkay wrote: |
if you reply you can't change the putting application in any way as well, I would reply, you want to make changes to how your system behaves, but can't change anything? That does not compute. |
That's the only reason I opened up this thread. To know if there is a way out given the constraints.  |
|
Back to top |
|
 |
smdavies99 |
Posted: Fri Jan 01, 2016 10:45 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
kash3338 wrote: |
That's the only reason I opened up this thread. To know if there is a way out given the constraints.  |
In the words of the song,
Somthings gotta give.
Because you have something reading from the queue you either have to change the flow writing to the queue OR the application/flow reading the messages as well as the changes to the MQ objects _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
PeterPotkay |
Posted: Fri Jan 01, 2016 11:01 am Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
You could create an MQ API exit that intercepts the MQPUT to this queue and modifies the behavior to do whatever it is you need. Good luck, may the Force be with you if you need to resort to this. _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
|