MQSeries.net :: View topic - WMB - PASSTHRU dump/trace

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » WMB - PASSTHRU dump/trace

Goto page Previous 1, 2

WMB - PASSTHRU dump/trace

« View previous topic :: View next topic »

Author

Message

smdavies99

Posted: Mon Jul 09, 2012 9:03 am Post subject:

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

If you had a properly designed and implemented logging/auditing framework this question would not arise.

I've seen several different implementations where both the commands and the returned values get logged as a matter of course.

In implementations what you are doing complicated joins in the SQL commands this is almost mandatory.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995

Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.

Gama

Posted: Mon Jul 09, 2012 9:33 am Post subject:

Centurion

Joined: 11 Jan 2005
Posts: 103
Location: Portugal

You are right....

Forget the database, ist's better for a plain text.

Gama

Posted: Tue Jul 10, 2012 2:22 am Post subject:

Centurion

Joined: 11 Jan 2005
Posts: 103
Location: Portugal

Hi, smdavies99

smdavies99 wrote:

I've seen several different implementations where both the commands and the returned values get logged as a matter of course.

Could you please detail and provide some more?

Thanks

smdavies99

Posted: Tue Jul 10, 2012 5:14 am Post subject:

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

To be brief because some of us get paid to do this for a living

IF you create an SQL command that will get executed on a DB OR Call a stored procedure you copy the full SQLCommand or the SP Params to a know area in the Environment tree. When the command has completed you copy the result to a similar known area.

At the end of the flow's operations this 'area' is written along with other data to a DB table.
If the flow errors out the same area is written with the ExceptionList in its entirety to anothe DB Table.
Naturally if you have also stored the incoming message is it's original unparsed (i.e. BLOB) form you are is a great prosition to find out what went wrong.

Not that long ago I used this to discover that a DB Admin had deleted a table that was crucial to our application. I was able to tell their manager exactly when it had happened (to within 2-3 minutes).

You do need to invest up fron in a proper Framework for your message flows. There is a lot more under the covers than what I've described here.

Even with all this in place, you sometimes have to deal with the developer who's attitude is 'I don't need no stinking logging' or 'I don't have time to code for it'. You just know that their code is going to be a can of worms.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995

Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.

Display posts from previous:

Goto page Previous 1, 2

Page 2 of 2

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » WMB - PASSTHRU dump/trace

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