Using IBM WebSphere Portal Trace Information for Troubleshooting


Tracing is an important tool for troubleshooting. In WebSphere Portal, you can trace information in logging and debugging messages, then use it to fix problems.


Enable tracing -- Use the Administrative Portlet in WebSphere Portal to set up tracing

You can set two types of traces in WebSphere Portal: temporary and extended. This article describes each one.

Temporary tracing

Temporary tracing only records information for the current session. Because tracing consumes a lot of system resources, the default is to have it turned off. Follow these steps to enable temporary tracing:

1. Login to WebSphere Portal as a user with administrative privileges. If you're using a default base install of WebSphere Portal, you'll login as "wpsadmin" .

2. Navigate to Administration > Portal Analysis > Enable Tracing. (As shown in the above figure)

3. In the Append these trace settings field (figure 1), enter the trace string "*=all=enabled" and click on the "+" sign to add this setting. You'll see a message that WebSphere Portal set the trace settings.

WebSphere Portal records the trace information in the wp_root/log/wps_date_time.log file (Windows/UNIX). You can also enable tracing for individual components.

Extended tracing

Extended tracing enables tracing for a longer period of time and for more than one session. Be cautious when choosing this option, because it's system- and resource- intensive. Follow these steps to enable tracing using this option:

1. Open "" file under wp_root/shared/app/config directory.

2. For the "#traceString" parameter, enter the trace string value (for example, #traceString=*=all=disabled).

3. This command will record trace information for your complete WebSphere Portal environment. This information is recorded in the wp_root/log/wps_date_time.log file (Windows/UNIX)

No comments:

Post a Comment

Recent Posts

Popular Posts

© 2011-2019 Web Portal Club