| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Information Wanted regarding Trace Node |
« View previous topic :: View next topic » |
| Author |
Message
|
| satyasheel15 |
 Posted: Mon Jun 16, 2003 12:53 am Post subject: Information Wanted regarding Trace Node |
 |
|
Voyager
Joined: 04 Mar 2003
Posts: 86
|
Question:
We have to work on the following project and I need suggestion/advise regarding the same:-
Project Idea:
We have to put XML Message as a Input and get the Swift Output using the MRM and Message Flow. For XML input, we are creating the MRM Message Set and for Swift also we are using the IBM provided Swift message set. So what we have to do that if in the message flow, incoming messages fails either due to parsing or syntax wrong, it goes to the fail queue. The Trace Node which is present between the Fail Queue and Input Queue is going to capture the ExceptionList and Body. But our requirement is that the output of the fail queue should contain the detail description of the error and the original input message in the form of XML message. So please tell , how to do that using the existing Trace Node or other IBM Primitives nodes.
How to capture the trace log into a queue along with the failed input message. This is our scope of work.
Awaiting a fast response.
Regards Always
Satyasheel |
|
| Back to top |
|
 |
| drajib |
| Posted: Mon Jun 16, 2003 1:49 am Post subject: |
|
|
Apprentice
Joined: 25 Mar 2003
Posts: 42
Location: India
|
Satyasheel,
Create a generic Error Handler subflow that would look for the innermost/deepest error within the Exception List tree. Either introduce a header (e.g. RFH2) or append a custom error structure to the end of the input XML structure, that would hold the captured detailed error message. Send the modified message to DLQ
Hope it helps.
Last edited by drajib on Mon Jun 16, 2003 2:35 am; edited 1 time in total |
|
| Back to top |
|
|
| drajib |
| Posted: Mon Jun 16, 2003 2:35 am Post subject: |
|
|
Apprentice
Joined: 25 Mar 2003
Posts: 42
Location: India
|
Just a curiosity, why do you need to create MRM message definitions for input XML messages! XML is self-describing right!
Or did you mean that you are importing DTDs within MRM! |
|
| Back to top |
|
|
| wmqiguy |
| Posted: Tue Jun 17, 2003 5:17 am Post subject: |
|
|
Centurion
Joined: 09 Oct 2002
Posts: 145
Location: Florida
|
Did something once upon a time along these lines:
Down the failure line, add a compute node that created the following type of message:
<MYERRORMESSAGE>
<ORIGINAL>Capture the original message as a BLOB here.</ORIGINAL>
<EXCEPTION_LIST>Attach the exception list here.</EXCEPTION_LIST>
</MYERRORMESSAGE>
I remember it being a pain because of different message formats and datatypes, etc. but finally created a version that was generic enough to handle all cases. We were also able to create a nice little flow that was able to strip the original message for reprocessing, as needed.
I'll take a look and see if I can locate the ESQL code to save you some time. 
Regards,
Todd |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
