| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Trace Node Usage |
« View previous topic :: View next topic » |
| Author |
Message
|
| saviobarr |
 Posted: Tue Oct 21, 2014 4:52 am Post subject: Trace Node Usage |
 |
|
Centurion
Joined: 21 Oct 2014
Posts: 100
Location: Sao Paulo, Brazil
|
Hi all,
I not quite familiar with Trace Node and its common use.
QUESTION: Is that correct put a Trace Node right after my first node in the flow?
The idea is to inspect every incoming message, when tracking down problems, by issuing a mqsichangetrace command.
Many Thanks
Savio Barros |
|
| Back to top |
|
 |
| ruimadaleno |
| Posted: Tue Oct 21, 2014 8:55 am Post subject: |
|
|
Master
Joined: 08 May 2014
Posts: 274
|
as far as i understand your requirement is to inspect the message your flows are receiving.
We have implemented a similar requirement (we want to know messages entering and exiting message flows) using record and replay.
Every message flow is built with monitoring events configured. This events (basically the messages) are kept in a database we can query to find problems, errors ,etc. Also we can user broker web admin console to check de messages.
have a look at knowledge center/documentation.
_________________
Best regards
Rui Madaleno |
|
| Back to top |
|
|
| kimbert |
| Posted: Tue Oct 21, 2014 11:45 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
The Trace node is a debugging tool - and a very useful one. It is not intended for use in production message flows.
For most debugging scenarios, the message flow debugger in the toolkit is a quick and easy way to inspect the message tree and step through your code ( ESQL or Java or .Net ).
When you need to inspect the message tree in more detail ( look at namespaces / field types etc ) or when you need to show a message tree to somebody else then the Trace node is a better option ( set the pattern to ${Root} )
_________________
Before you criticize someone, walk a mile in their shoes. That way you're a mile away, and you have their shoes too. |
|
| Back to top |
|
|
| MB Developer |
| Posted: Tue Oct 21, 2014 8:11 pm Post subject: |
|
|
Disciple
Joined: 03 Feb 2014
Posts: 179
|
It is better way to find errors in msg flow by using TRACE node ...
Sample :
MQInput Node --> Compute Node --> MQOutput Node
Now Connect MQInput Node Failure and Catch Terminal to Trace node.
Set Trace Node Properties :
Basic -- Destination -- File
File Path -- D:\MB_Development\sample.txt
Pattern : ${CURRENT_TIMESTAMP}
Exception List : ${ExceptionList}
----------------------------------------------------------------------
In MQInput Node Set:
Input Message parsing -- Message Domain -- XMLNSC : For XML messages (namespace aware, validation, low memory use)
Compute Node Just write code like below :
-- CALL CopyMessageHeaders();
--CALL CopyEntireMessage();
SET OutputRoot.XMLNSC.Employee = InputRoot.XMLNSC;
Enable debugger ....
Then put msg in Input Queue Other then XML format and Find in Trace node File path location ....
_________________
Thanks.... |
|
| Back to top |
|
|
| saviobarr |
| Posted: Wed Oct 22, 2014 5:08 am Post subject: |
|
|
Centurion
Joined: 21 Oct 2014
Posts: 100
Location: Sao Paulo, Brazil
|
Thanks a lot. All replies were very helpful. javascript:emoticon(' ') |
|
| 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
|
|
|
|
