| Author |
Message
|
| MVO |
 Posted: Thu Dec 13, 2001 10:37 am Post subject: |
 |
|
Centurion
Joined: 09 Sep 2001
Posts: 131
|
We're running MQSI 2.0.2 on NT and Sun Solaris. Our application requires detailed loggings of all incoming and outgoing messages. Currently the MQOutput node only has a failure terminal. Any plan to add an output terminal to it ? we'd like to put a with option NEW_MSGID but without the output terminal, we have no way of knowing the MQSeries-assigned MsgId. For now, we have to manually build the MQ MsgId before the put. This is not a good approach to guarantee uniqueness of MsgId especially in case of disaster recovery.
|
|
| Back to top |
|
 |
| EddieA |
| Posted: Thu Dec 13, 2001 2:45 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
That wouldn't work because it's MQ that generates the unique MessageID on the PUT and there's no MQ option to just generate that MessageID.
If you want MQSI to generate the ID, then why not just generate the message ID yourself, the same way that MQ does:
AMQ space <qmgr name> <some kind of timestamp>
Or for real over-kill, you could always make the output queue from the flow the input queue to a second flow that just captures the information you want and then pass the message on to it's final destination.
Cheers,
_________________
Eddie Atherton
IBM Certified Specialist - MQSeries
IBM Certified Specialist - MQSeries Integrator
[ This Message was edited by: EddieA on 2001-12-13 14:45 ] |
|
| Back to top |
|
|
| NickB |
| Posted: Fri Dec 14, 2001 2:08 am Post subject: |
|
|
Centurion
Joined: 20 May 2001
Posts: 107
Location: Zurich Financial Services
|
| If you need to generate a truly unique message id then suggest you use the UUID support pac (IA0L). This works well (tested on both NT and AIX successfully). You need to tailor the node so that the unique number is inserted in to "Root.MQMD.MsgId". |
|
| Back to top |
|
|
| zpat |
| Posted: Fri Dec 14, 2001 8:39 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5849
Location: UK
|
UUID function is standard in ESQL with WMQI version 2.1
MQ Output nodes have two terminals (out and failure) (at least in WMQI 2.1 they do). |
|
| Back to top |
|
|
| Miriam Kaestner |
| Posted: Mon Dec 17, 2001 3:41 am Post subject: |
|
|
Centurion
Joined: 26 Jun 2001
Posts: 103
Location: IBM IT Education Services, Germany
|
...and in WMQI 2.1 the MQOutput node writes information on the message(s) sent to LocalEnvironment.WrittenDestination
Any downflow node can access this information. |
|
| Back to top |
|
|
| bmccarty |
| Posted: Wed Dec 19, 2001 12:10 pm Post subject: |
|
|
Apprentice
Joined: 18 Dec 2001
Posts: 43
|
With WMQI 2.1 you can also write your own custom plug-in nodes in Java or C. In this way you could create one where you can define as many output terminals as you like that writes data or messages to anywhere such as a directory or FTP site or log file.
You could even set some Message Flow specific parameters to take level of logging like 1,2 or 3 depending on the detail that you want outputed.
If you want some example code let me know and I will post it. |
|
| Back to top |
|
|
| MVO |
| Posted: Wed Dec 19, 2001 12:26 pm Post subject: |
|
|
Centurion
Joined: 09 Sep 2001
Posts: 131
|
| thanks all for your help. Yes, I would appreciate some sample codes. |
|
| Back to top |
|
|
|
|
