The functionality described in this article is available in meshIQ Manage versions 12.1 and greater.
For a quick overview of what's new or changed, visit the meshIQ Highlights page for a version-by-version breakdown.
Jump to Section:
Version 12.x and Later
Version 11.3 and Earlier
Version 12.x and Later
The Trace Commands option in an IIB/ACE integration server allows administrators and developers to enable, reset, and stop tracing at both the service and user levels. These traces help diagnose system-level issues or debug application-level message flows. Each trace type can be controlled independently using the Start, Reset, and Stop commands.
Service Trace
Service trace captures deep internal processing of the integration server, including system calls, runtime components, and broker operations. It is typically used for advanced troubleshooting or when directed by IBM Support.
Start Service Trace: Initiates system-level tracing.
Reset Service Trace: Clears existing trace logs to begin a fresh trace session.
Stop Service Trace: Stops system-level tracing and finalizes the trace file for analysis.
User Trace
User trace captures application-level debugging details, including message flow execution paths and node-level behavior. It is mainly used by developers during testing or debugging.
Start User Trace: Begins user-level trace logging.
Reset User Trace: Clears previous user trace data before new trace activity is captured.
Stop User Trace: Ends user-level tracing and prepares trace data for review.
Performing Trace Commands
To access trace commands for an integration server:
In the Server widget, select the integration server.
From the Selected menu, choose Trace Commands.
-
Select the desired option:
Service Trace → Start / Reset / Stop
User Trace → Start / Reset / Stop
Actions are applied immediately, and a success notification appears at the bottom of the window once the action is completed.
_________________________________________________________________________________________________________________
Version 11.3 and Earlier
The Trace Commands option in an IIB/ACE integration server allows administrators and developers to enable, reset, and stop tracing at both the service and user levels. These traces help diagnose system-level issues or debug application-level message flows. Each trace type can be controlled independently using the Start, Reset, and Stop commands.
Service Trace
Service trace captures deep internal processing of the integration server, including system calls, runtime components, and broker operations. It is typically used for advanced troubleshooting or when directed by IBM Support.
Start Service Trace: Initiates system-level tracing.
Reset Service Trace: Clears existing trace logs to begin a fresh trace session.
Stop Service Trace: Stops system-level tracing and finalizes the trace file for analysis.
User Trace
User trace captures application-level debugging details, including message flow execution paths and node-level behavior. It is mainly used by developers during testing or debugging.
Start User Trace: Begins user-level trace logging.
Reset User Trace: Clears previous user trace data before new trace activity is captured.
Stop User Trace: Ends user-level tracing and prepares trace data for review.
Performing Trace Commands
To access trace commands for an integration server:
In the Server viewlet, select the integration server.
From the Selected menu, choose Trace Commands.
-
Select the desired option:
Service Trace → Start / Reset / Stop
User Trace → Start / Reset / Stop
Actions are applied immediately, and a success notification appears at the bottom of the window once the action is completed.