Starting user trace

Use user trace for debugging your applications; you can trace integration nodes, integration servers, and deployed message flows. Start user trace facilities by using the mqsichangetrace command, the web user interface, or the REST API.

Before you begin

Before you start to trace an integration node, an integration server, or a deployed message flow, the integration node or server must be running. For more information, follow the instructions in the Deploying integration solutions topic.

About this task

To start a user trace, complete the following steps.

Procedure

  1. Start IBM® App Connect Enterprise user trace facilities by using the mqsichangetrace command, the web user interface, or the REST API:
    • Specify the -u parameter on the mqsichangetrace command.
    • In the IBM App Connect Enterprise web user interface, select Start user trace from the options list.
    • Use the REST API provided by IBM App Connect Enterprise.
    You can select only one integration node or server on each invocation of the command, but you can activate concurrent traces for more than one integration node or server, by invoking the command more than once.
  2. Specify an individual integration server or message flow within the specified integration node to limit the scope of a trace.
    The events that are recorded when you select the message flow option include:
    • Sending a message from one Message Processing node to the next
    • Evaluating expressions in a Compute or Filter node
  3. Start your trace.
    You can start trace at two levels:
    normal
    This tracks events that affect objects that you create and delete, such as nodes.
    debug
    This tracks the beginning and end of a process, as well as monitoring objects that are affected by that process.

Example: starting user trace for an integration server

About this task

To start normal level user trace for integration server integrationServer1 on integration node INODE, enter the command
mqsichangetrace INODE -u -e integrationServer1 -l normal
where:
-u specifies user trace
-e specifies the integration server (in this case, integrationServer1)
-l specifies the level of trace (in this case, normal)