Capturing Traces in IIB OR ACE

 

User Trace

User trace is normally used by IIB Developers to aid debugging message flow the result of each node and ESQL/Java statement is logged to the trace.

Service Trace

Service trace is - as the name suggests - normally used by IBM service teams to analyse problems. Service trace produces very detailed output the format of which is not publicly available. You will often be asked to produce a service trace as part of the PMR process. The IIB Knowledge Centre has this to say about service trace:

"..Activate service trace only when you receive an error message that instructs you to or when directed to do so by your IBM Support Center.."

Collecting "User Level" Trace for an ACE Integration Server

This method of enabling trace requires an Integration Node.

If you are using a stand-alone Integration Server, you cannot use the mqsichangetrace command.

1. 1. Start trace:
   mqsichangetrace <Int.Node> -e <Int.Server> -u -l debug -r -c 200000 
2. 2. Re-create the runtime behavior.
3. 3. Stop trace:
   mqsichangetrace <Int.Node> -e <Int.Server> -u -l none 

Additional Information

Output location

Traces are written to the Integration Server's workdir or the multi-user work path:

 - <workdir>/config/common/log

 - /var/mqsi/common/log

Performance Impact
A "user level" trace logs a high level view of message flow processing within Int.Server and therefore can have some impact to performance.
Take care when enabling trace in production and other high throughput environments.

 

Maximum file size

ACE component traces have a maximum file size.
When the maximum file size is reached, the tracing mechanism overwrites the oldest trace data.

The '-c' flag on the mqsichangetrace command overrides the maximum size for the trace, in KB.

Collecting "Service Level" Trace for an ACE Integration Node

This method of enabling trace uses the same mqsi* commands as previous versions of IBM Integration Bus (IIB).

1. Start trace:

   mqsichangetrace <Int.Node> -b -t -l debug -r -c 200000

   
   
2. Recreate the runtime behavior.
3. Stop trace:

   mqsichangetrace <Int.Node> -b -t -l none

Additional Information

Output location

Traces are written to the Integration Server's workdir or the multi-user workpath:

 - <workdir>/config/common/log

 - /var/mqsi/common/log

Performance Impact 
A "service level" trace logs the internal function calls within Int.Node processing and therefore can have an impact to performance. 
Take care when enabling trace in production and other high throughput environments.

 

Maximum file size

ACE component traces have a maximum file size. 
When the maximum file size is reached, the tracing mechanism will begin to overwrite the oldest trace data.

The '-c' flag on the mqsichangetrace command, or the traceSize in the node.conf.yaml file, overrides the maximum size for the trace, in KB.

 

Capturing startup events

The mqsichangetrace command can be run with the Int.Node stopped. 
Updating the node.conf.yaml file requires the Int.Node to be restarted. 
Enabling trace in either of these ways will trace startup activities.

We can enable trace for JDBC, ODBC, HTTP listener, SSL, Java etc.  see below link-

https://www.ibm.com/support/pages/index-app-connect-enterprise-and-ibm-integration-bus-trace-directions

https://www.ibm.com/support/pages/tracing-and-debugging-iib-message-flows-0

Service Trace --

mqsichangetrace ACEORNG-TEST -e TGCS_HTTPS_PROXY -t -l debugTree -r -c 200000 

[aceuser@~]$ mqsichangetrace ACEORNG-TEST -e TGCS_HTTPS_PROXY -t -l debugTree -r -c 200000

BIP8071I: Successful command completion.

[aceuser@~]$ mqsireporttrace ACEORNG-TEST -e TGCS_HTTPS_PROXY

trace

  userTrace

    level='none'

    traceSizeKb=1048576

    mode='safe'

  serviceTrace

    level='debugTree'

    traceSizeKb=200000

    mode='safe'

    stopOn=''

  traceNodes

    enabled='on'

BIP8071I: Successful command completion.

[aceuser@~]$

[aceuser@~]$ mqsichangetrace ACEORNG-TEST -e TGCS_HTTPS_PROXY -t -l none

BIP8071I: Successful command completion.

[aceuser@tuat2ace01 ~]$ mqsireporttrace ACEORNG-TEST -e TGCS_HTTPS_PROXY

trace

  userTrace

    level='none'

    traceSizeKb=1048576

    mode='safe'

  serviceTrace

    level='none'

    traceSizeKb=200000

    mode='safe'

    stopOn=''

  traceNodes

    enabled='on'

BIP8071I: Successful command completion.

[aceuser@~]$