Comments on: Avoid the WebSphere Integration Developer Debugger

By: Pavel Trka

Pavel Trka — Thu, 24 Apr 2008 09:10:37 +0000

Yeah, we also use higher levels of WebSphere tracing – just few days ago it helped us very much in identifying problem with built in staff verb “Group” – it seemed that it’s not working but thanks to trace we saw that although LDAP itself is case insensitive, the way WPS handles group names when using this verb leads to case-sensitive operation – trace was displaying sql queries that are used for access rights recognition and we immediately saw whats going on.

I also forgot to mention Audit Trail and Failed Event Manager which both can be used for gathering debug information

By: dan

dan — Wed, 23 Apr 2008 15:22:15 +0000

Yeah, what I do is leverage WebSphere Tracing for my debugging. That way the code can go into production and get reused should a issue occur there.

By: Pavel Trka

Pavel Trka — Wed, 23 Apr 2008 15:17:20 +0000

Hi,
it was one of the first things I noticed when I started to develop in WID – the debugger is absolutely useless…

For debugging purposes we have to use many debug logs in our processes, sometimes it’s the only way to know what is really happening

By: dan

dan — Mon, 21 Apr 2008 14:48:12 +0000

Hi Akram,

Thanks for the kind words. I’m glad you are able to find value in what I have to offer.

By: Akram Chotu

Akram Chotu — Sat, 19 Apr 2008 14:00:25 +0000

I also work with WID, WPS, WTX etc. in Healthcare domain. Your blog is really useful to me and I thank you for taking time in sharing your knowledge. Keep up the good work.