How can I troubleshoot problems?

New users: Use the links in this topic to find out how to debug message flows and get help with troubleshooting problems.

How can I debug and troubleshoot my message flows?

A number of tools and sources of information are available to help you solve problems with your message flows. If you can see errors or warnings in the Problems view in the IBM® App Connect Enterprise Toolkit, your message flows and related resources might have problems that prevent you from adding them to a BAR file. Also, your message flows might not work as you expect when they are deployed.

Use the information in the error or warning messages to fix the problem. If you have difficulty deploying message flow resources, see How can I troubleshoot problems when deploying message flows? in this topic for more information. If you have successfully deployed your message flows, you can use the following links to debugging and troubleshooting topics to help you solve any problems.

  • How do I use the flow debugger?

    You can test and debug your message flows by using the debugger in the IBM App Connect Enterprise Toolkit. By adding breakpoints to your message flows, you can use the debugger to view the path that messages take through your message flow. You can also view the contents of the message passing through the flow, and step through code to view the output messages being constructed. The debugger is launched from the Debug perspective.

  • Where can I find useful logs?

    Find out where to find useful logs that are used in IBM App Connect Enterprise.

  • How do I use trace?
    User trace can be used to get further information about problems with messages passing through your message flows. You can use the following task to get user trace to troubleshoot a problem with a message flow:
    1. User trace example

Where can I get other help on troubleshooting and solving problems?

Use the links in this section to find out more information about troubleshooting and how to get support.