| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Tracking and archiving all messages |
« View previous topic :: View next topic » |
| Author |
Message
|
| viks |
 Posted: Wed Oct 16, 2013 9:36 pm Post subject: |
 |
|
Newbie
Joined: 12 Jun 2013
Posts: 8
|
| smdavies99 wrote: |
What about using Alias Queues to avoid having all the clients change their endpoints? |
Right now publisher A put message to Q1 and consumer B get message from same queue Q1. So either A or B need to change their endpoint. say Q2, and I won't be able to alias Q2 by Q1, as Q1 already exists. |
|
| Back to top |
|
 |
| gbaddeley |
| Posted: Thu Oct 17, 2013 2:41 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| viks wrote: |
| gbaddeley wrote: |
It is far easier and more reliable for an application to write MQ messages to a database or an application log immediately after producing or consuming each message. |
In our case we have 100 or more producer and consumer applications, so it' easier to do this ourselves than asking each application to do it.
|
Its easier to burden yourself with designing, implementing and forever maintaining a solution that really belongs in the application space, not the infrastructure space? I hope you are properly prepared for this.
| viks wrote: |
| gbaddeley wrote: |
What are you going to do with the messages?
|
There is an application which needs all these messages that is been archived, for certain calculation/processing. |
Ahh, so its not to archive or log messages for an audit or backup requirement, its an application requirement for additional processing. I think you need to engage your enterprise architects and designers to come up with a proper solution that is embedded in the applications, where it belongs.
_________________
Glenn |
|
| Back to top |
|
|
| Cressida |
| Posted: Mon Oct 21, 2013 3:10 am Post subject: |
|
|
Disciple
Joined: 13 Jul 2007
Posts: 157
|
If we are talking Replication for use by another application or for DR purposes, we would like to get SynQuest a proper mention as well ...
| viks wrote: |
……… So for that I need to replicate all the messages to an another queue while the existing message transfer doesn't get affected. I've seen number options, but not sure which is the best ( or most used ). Of course since applications are already started using the environment, we don't want to change the publishing/consuming queues if possible.
While doing some research here the options that I came across are given below.
1) using an API exit , MirorQ:
Advantages: No need to change the queue names. Easier to setup.
Disadvantage: Not sure MirrorQ is an ideal one to sue in production. Only found 32-bit version. Performance could be an issue. |
How about a more advanced, fuller featured, vendor supported, multi-platform AND MQ Explorer integrated MirrorQ alternative :
http://www.cressidatechnology.com/mqproducts_synquest.html
and, should there remain any Tracking and Auditing of Messages based on already collected MQ Logs data, Circular or Linear, Archived or not ..... should be able to find relevant info on another part of that same website ...
 |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
