Configuring WebSphere Application Server logging

You can configure logging for WebSphere Application Server.
About this task
Use the WebSphere® Application Server Administrative console to set up and configure WebSphere logging and tracing. You can use the following URL to access the Administrative console:
http://server-name:admin-console-port-number/ibm/console
where the variables have the following meanings:
server-name
Name of the CM Server computer
admin-console-port-number
Administrative console port number: 12060 by default with CM Server, or 9060 for other WebSphere Application Server versions
Attention: Any level of tracing (FINE, FINER, or FINEST) for any component running in WebSphere Application Server, including the CM Server components, will have a negative impact on performance.

Depending on the type of Websphere Application Server running on your CM Server system, you might be able to make changes in real time without having to stop and restart the CM Server.

On most Administrative console log setup pages, there are two tabs: Configuration and Runtime.

To configure WebSphere Application Server logging and tracing, perform the following steps:

  1. From the Administration console, click Troubleshooting > Logging and Tracing, and select the server to configure.
  2. Select Change Log Detail Level and click the Runtime tab. Changes made to the Runtime tab take effect as soon as you save them. Changes made to the Configuration tab do not take effect until you restart the server.
    1. Select the Save runtime changes to configuration as well check box if you want the changes to persist.
    2. Click the Components link. Note that *=info is listed in the box.
    3. Open the option com.ibm.rational.* and select com.ibm.rational.stp.*.
    4. Click the Message and Trace Levels option to select the level.
    5. Click OK. Then click Save in the Messages area at the top of the page that opens. Changes take effect without restarting the server.
  3. If the version or class of Websphere Application Server on your CM Server system does not provide a Runtime tab that enables real-time configuration changes, use the Configuration tab. Then restart the server to affect the saved changes.
  4. You will probably need to increase the default settings for the log file size and the number of log files to rotate. Set the number of log files to rotate through to at least 20, and set the log file size to at least 20 MB. Use the WebSphere Administrative console to change the JVM log file size and file rotation settings:
    1. Select Troubleshooting > Logging and Tracing.
    2. Select the relevant server from the list of servers to configure.
    3. Select JVM Logs. Then click the Configuration tab. (You can use the Runtime tab to view the current SystemOut.log and SystemErr.log file contents.)
    4. Modify the SystemOut and SystemErr locations, file sizes (should be at least 20 MB), and how many historical files to maintain (should be at least 20 MB).
    5. Click OK. Then click Save in the Messages area at the top of the page that opens.
    WebSphere Application Server log files are written to the following locations:
    • UNIX®: /opt/rational/common/CM/profiles/cmprofile/logs/server1/
    • Windows®: \Program Files\IBM\RationalSDLC\common\CM\profiles\cmprofile\logs\server1\

Feedback