ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Debugging message flow

Post new topic  Reply to topic
 Debugging message flow « View previous topic :: View next topic » 
Author Message
Paul
PostPosted: Tue May 25, 2004 4:52 am    Post subject: Debugging message flow Reply with quote

Newbie

Joined: 25 May 2004
Posts: 3

What is the best way to debug and test a message flow?

Thanks in advance,
Paul
Back to top
View user's profile Send private message
waugh
PostPosted: Tue May 25, 2004 5:01 am    Post subject: Reply with quote

Master

Joined: 19 Feb 2004
Posts: 225

what versions of softwares you are using? i think that helps us a bit...
Back to top
View user's profile Send private message
Paul
PostPosted: Tue May 25, 2004 5:06 am    Post subject: Reply with quote

Newbie

Joined: 25 May 2004
Posts: 3

I am using WMQI 2.1.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Tue May 25, 2004 5:28 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

What kind of testing and debugging do you want to do?

For unit testing - I prefer to develop a set of test messages, and then include trace nodes at key points in the flow. Then I can run the messages through the flow, and see if they generate the right output. I can also see crucial pieces of the message transformation through the trace output.

The test cases can then be rolled into integration testing and performance testing at a later time.

For developmental debugging, I'll tend to put lots of stuff into the Environment subtree, and again expose that through the trace nodes. I reserve using the step-by-step debugger for those cases where I can't tell what steps are occurring from the outputs. Although user-level tracing and debug-level tracing will also show that without needing to step through the flow.

But this is all just my own personal opinion - and not necessarily best practices.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
Paul
PostPosted: Tue May 25, 2004 5:47 am    Post subject: Reply with quote

Newbie

Joined: 25 May 2004
Posts: 3

Thanks Jeff,just tell me one more thing.There are existing flows which I have to debug.how to put stuff into Environment tree??
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Tue May 25, 2004 6:04 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

You'd have to change the flows.

For existing flows, your best bet is probably a usertrace.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Debugging message flow
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.