Enable trace diagnostics
You can enable logging and tracing in order to debug problems using
EIF WebSphere JMS Provider. Logging and tracing can be enabled for the two
components, JMS provider component and event converter and forwarder
component of the EIF WebSphere JMS Provider.
Enabling JMS Provider component trace diagnostics
To enable logging and tracing of the JMS provider component, follow
these steps :
- In the WebSphere administrative console, click
Troubleshooting>Logs and Trace.
- In the list of servers, click the server where the EIF WebSphere JMS Provider
is installed.
- Click Change Log Detail Levels
- In the list of groups, click com.ibm.wtci.*
- Click the trace type you want to enable
- Click OK and save the configuration.
The trace specification is updated to reflect the trace type you
selected. For example, to turn on all tracing for the JMS provider
component of EIF WebSphere JMS Provider, the trace specification would be
com.ibm.wtci.*=all.
Log files are written to the location configured for the WebSphere
server.
Enabling event converter and forwarder component trace diagnostics
To enable logging and tracing of the event converter and forwarder
component, follow these steps:
- In the WebSphere administrative console, expand the Resources List.
- Click JMS Provider > Generic.
- Select the scope of the resources to be the node, choosing the node
on which the EIF WebSphere JMS Provider is installed.
- Click EIF JMS Provider>JMS connection
factories>TECQueueConnectionFactory>Custom
properties>LogLevel.
- Set the value of the property to ALL.
- Click OK.
- Select the TraceLevel.
- Set the value of the property to ALL.
- Click OK
- Select LogFileName
- If desired, modify the value of the property, setting it to the
location and name of the log file.
- Click OK.
- Select TraceFileName
- If desired, modify the value of the property, setting it to the
location and name of the trace file.
- Click OK and save the configuration.
If you had reconfigured the system, use the scope at which EIF WebSphere JMS Provider configuration is installed and choose the appropriate JMS
connection factory.
WebSphere Application Server needs to be restarted for the configuration
changes to take effect.
Related topics
Troubleshooting common
problems
Parent topic
Overview