on 05-22-2012 6:02 AM
Hello everybody,
A couple of minutes ago I learnt the hard way we have to be very careful with the use of Workflow Trace (Transaction SWU8 / SWU9 / SWF_TRC)
I ended up with a couple of TIME_OUT short dumps for WF-BATCH... which made me wonder...
1. Anybody here have used Workflow Trace Utility? Was it useful at all?
2. There were only 20 instances traced... Was that amount of processing enough for the TIME_OUT? And I know there is a lot of "well, that depends..." in this one.
Thanks a lot for reading.
Cheers,
Andres.
The workflow trace can be turned on from SWUD, or from SWU8 (you would
use SWU9 to display the trace.)
This trace gives you a very detailed picture of what is going on inside your
workflow, from workflow to task, and so forth.
Double-clicking on a CONTBINDEXECUTE step will show you the details of binding.
Again, you can drill down for details on the binding, and you will see information similar to that of the
Container Monitor. The difference is, the Workflow Trace will track all steps,
dialog or background, and will live for the duration of the workflow.
It is advised that you do NOT have the workflow trace turned on (or leave it
turned on for any length of time) in a production system.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Yous should use Workflow Trace if you do not find any solution what is going on for some particular provlem. Otherwise it is better not to use in Production system.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Check this thread.You may find the details.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
25 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.