You can specify how a WebSphere® Application
Server handles log records. You can enable or disable a system log
for a server, specify where log data is stored, and choose a format
for log content. You can also specify a log detail level for components
and groups of components.
About this task
In a clustered environment, perform these steps for each
node in the cluster.
Procedure
- Log in to the WebSphere Integrated
System Console as the administrator.
- In the navigation pane, click .
- Click the name of the Sametime® server, for example STMeetingServer.
If components are stored on different servers, click the name of the
server component you want to change.
- In the General Properties section, click Diagnostic
Trace
- In the Additional Properties section, click Change
log detail levels.
- Choose whether to make configuration or runtime changes.
- Expand the Components and Groups section.
Click a component name to select the log level from a context menu.
Each setting you select is appended to the default
*=info
setting,
and appears in the text box. A colon (:) followed by a space is appended
to each setting as a delimiter.For example, if you
select the setting
com.ibm.rtc.*=all
, the following
text displays in the text box:
*=info: com.ibm.rtc.*=all
To
see the recommended settings to use for diagnostic trace, see Recommended trace settings.
- Click Apply.
- Save the change to the master configuration by clicking
the Save link in the "Messages" box at the
beginning of the page.
Note: This step is needed only if
you made changes on the Configuration tab,
or if you made changes on the Runtime tab,
and then selected Save runtime changes to configuration
as well.
- Optional: You can monitor the log files in
the profiles directory:
AIX® and Linux™:
/opt/IBM/WebSphere/AppServer/profiles/Profile_Name/logs
Windows™:
WAS_Install_Root\WebSphere\AppServer\profiles\Profile_Name\logs
- If you made changes in the Configuration tab,
restart the server.
- Optional: When you have identified and fixed
the problem, free up system resources by reverting the trace level
back to its default
*=info
setting.