USER LEVEL TRACE AND SERVICE LEVEL TRACE

Use this procedure to capture a user or service level trace of an IBM Integration Bus (IIB) message flow at an Integration Server level or a Web Sphere Message Broker (WMB) message flow at an execution group level.

User Level Trace : User trace provides more information than that provided by the entries that are written to the logs. Typically, you use user trace for debugging your applications, as it can trace brokers, execution groups, and deployed message flows.

Service Level Trace : Service trace provides more detailed information than that provided by the entries that are written to the Syslogs, Event Logs, Trace Node Outputs, or User Trace. Typically, IBM support uses service trace for debugging problems as it can trace internal calls in addition to the brokers, execution groups, and deployed message flows.

User Level Trace:

1. Start trace.

Open your IBM Integration console of related developer edition, in that just type below commands.

mqsichangetrace <brokername> -u -e <egroup> -l debug -r -c 50000

<brokername>---> name of the broker

-u ---> user level trace

<egroup>---> name of the executiongroup

-l ---> changing modes (none,debug)

-r ---> reading the content of user trace

-c ---> stored logs file size (in KB's)

The above command is used to capture the user level trace. We are changing none mode to debug mode for tracing the logs.

2. Put a message on the input node queue and complete the flow.

3. Retrieve the trace log for the specified component.

mqsireadlog <brokername> -u -e <egroup> -f -o flowtrace.xml

We will get trace logs in the form of 'xml'; need to convert into text format.

4. Format XML tracefile.

Here we are converting xml to text format.

mqsiformatlog -i flowtrace.xml -o userflowtrace.txt

5. The userflowtrace.txt will be in the current working directory. EX. C:\Program Files\IBM\IIB\10.0.0.16. With the specified name.(flowtrace.xml and userflowtrace.txt).

Note: we can stop trace by typing below command

mqsichangetrace <brokername> -u -e <egroup> -l none

Service Level Trace:

1. Start trace.

mqsichangetrace <brokername> -t -e <egroup> -l debug -r -c 100000

<brokername> ---> name of the broker.

-t ---> service level trace

<egroup> ---> name of the executiongroup

-l ---> changing modes (none,debug)

-r ---> reading the content of service trace

-c ---> stored logs file size (in KB's)

2. Put a message on the input node queue and complete the flow.

3. Retrieve the trace log for the specified component.

mqsireadlog <brokername> -t -e <egroup> -f -o serflowtrace.xml

Need to convert xml to text. B/z logs will store in the form of xml.

4. Format XML tracefile.

Here we are converting xml to text format.

mqsiformatlog -i serflowtrace.xml -o serflowtrace22.txt

5. The userflowtrace.txt will be in the current working directory. EX. C:\Program Files\IBM\IIB\10.0.0.16. With the specified name. (serflowtrace.xml and serflowtrace22.txt).

Note: we can stop trace by typing below command

mqsichangetrace <brokername> -t -e <egroup> -l none