TEC Workbook - IBM

1.13 Logging
IBM Software
WebSphere DataPower appliances have a built-in publish-subscribe logging mechanism that is robust
and flexible. As transactions flow through the appliance, many events occur. Some of these events occur
as a result of normal processing, while others occur as a result of an exception such as a transaction
being rejected due to an authentication or authorization failure.
1.13.1 Setting the Logging Level to Debug
By default, the logging level is set so that only messages with a maximum priority of “Error” are written to
the system log. In this section, you’ll change the default log level to “debug”, resulting in a much more
granular level of logging. This not only is helpful is seeing what steps are executing, but helps in
troubleshooting when things aren’t going as expected.
__1. In the Logging section, change the Log Level dropdown to: debug
__2. Click the Set Log Level button to activate the change.
__3. In the Confirmation window, click the Confirm button.
__4. Click the Close button to dismiss the window.
Throughout the various configuration forms, there are links that enable you to view the logs. For
example, right above the Log Level is a magnifying glass icon that, when clicked, will open a window
showing the system log. You can also view the log from the main control panel.
__5. Click on the Control Panel link in the upper left corner of the browser window.
__6. In the Monitoring and Troubleshooting section, click on the View Logs.
Clicking on the View Logs icon will take you to the system log page, which by default shows the last 50
entries in the default log. The interface enables you to filter the entries by category and/or priority, in
order to limit the number of lines.
Lab 1 – Introduction WebSphere DataPower SOA Appliances Page 21