| Author |
Message
|
| naek |
 Posted: Thu Jan 18, 2007 1:21 am Post subject: Queue Archiving / Logging |
 |
|
Newbie
Joined: 10 Jan 2007
Posts: 6
|
Hello
I want to know is it possible to archive/log every message that arrived/departed into/from a queue without any modification to code which send the message ( by specify the report). I want the configuration only takes part in Queue Manager or by means of administrative configuration task only.
I want it as a mechanism of message journaling in my application.
The term "archive" or "logging" may not appropriate in this context but I hope all of you understand what I mean.
I use MQ 5.3 on Windows 2003. |
|
| Back to top |
|
 |
| Mr Butcher |
| Posted: Thu Jan 18, 2007 1:27 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
api exit (if application is connected to you rqueuemanager) and or channel message exit (incoming / outgoing messages via channel) is what you need.
but i recommend to include application journaling in the application.
_________________
Regards, Butcher |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Jan 18, 2007 2:15 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The sample API exit "mirrorq" does exactly this.
There are several things you need to consider, though.
1) What are you going to do with these duplicate messages? Just leave them sitting on a queue?
2) How important is this function? Is it worth doubling the load on your queue manager?
3) Is it allowable under your policies to implement an entirely unsupported code sample in production?
I'm with Mr Butcher - I recommend application journalling in the application.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Tibor |
| Posted: Thu Jan 18, 2007 8:25 am Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
| If you have a message broker in the MQ environment, you can use it to log the messages. |
|
| Back to top |
|
|
| naek |
| Posted: Sat Jan 20, 2007 11:27 pm Post subject: |
|
|
Newbie
Joined: 10 Jan 2007
Posts: 6
|
Hi all thanks for your suggestion. API exit exactly what I need to solve my queue journaling problem.
It is very important in my application to log every message that arrives into the queue as one way of application audit. The mirror queue will be processed at 'cut off' time and than going to application report. Modify current application is not possible because of some development restriction.
Event currently API exit solves my problem, I actually curious what actually going on behind the scene, and why "exit" term is used in that context, any good resource references are welcome.... |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Sun Jan 21, 2007 6:15 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
An exit is a place where the queue manager code executes user-written code inside it's own process.
It's like a plugin.
If the application can't be built to meet a business requirement, and "audit trail" and "application report" are both business requirements, then the development team is not doing their job.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
