I have part of my application using MQ Workflow to call Java components; several activities executing one after the other based on the "ResultCode".
I feel this acts like a "Black box" and i am not familiar with the WF call / working mechanism ( i am not working on WF) the only way the application is debugged is from the log files (log4j used in java code).
this is the only way i can get to know any problem in the application.
even if there is really problem in the WF model or FDL definition its only the logs we need to analyze to find the problem is really with java code or WF definition.

is there any way to log "calls" within the WF and log it separately so it will be helpful to navigate the WF logs to find the problem ?
is there any way to do this ?
please help, since this becomes a huge problem when debugging with a larger application.

Hi,

unfortunately I must tell you that MQWF is not a product that you can just
install and work with
without dealing with its concepts. That means: reading the books that come
with MQWF
(Concepts, Installation Guide, Administration Guide, Buildtime, etc.).

In the Administration Guide you'll find a chapter that deals with the
auditing features of MQWF.
I think that will satisfy your requirements. Good Luck!

Volker Hoss
IBM WebSphere Process Server Development

Volker,
Thanks a lot for your response; there is a special WF guy to do this work.
Is there any methodology can be proposed to do this stuff? As you said we can enable the Auditing features in MQWF. Can you plz describe any hands on stuff to get our hands wet?

Your help is highly appreciated.