Trace

If you cannot get enough information about a particular problem from the entries that are available in the various logs, the next troubleshooting method to consider is using trace. Trace provides more details about what is happening while code runs. The information produced from trace is sent to a specified trace record, so that you or IBM® support personnel can analyze it to discover the cause of your problem.

Trace is inactive by default, and must be explicitly activated by a command, or by the IBM Integration Toolkit.

There are two main types of trace available in IBM Integration Bus: user trace and service trace. Typically, you utilize user trace for debugging your applications; you can trace integration nodes, integration servers, deployed subflows, and deployed message flows. With service trace, you can activate more comprehensive integration node tracing, and start tracing for the IBM Integration Toolkit. You can also trace the execution of all the commands described in Commands.

When you start user tracing, you cause additional processing for every activity in the component that you are tracing. Large quantities of data are generated by the components. Expect performance to be affected while trace is active. You can limit this additional processing by being selective about what you trace, and by restricting the time during which trace is active.