Use the Integrated Solutions Console to
specify how data is logged, where the log data is stored, and the
output format to use for log data.
About this task
You can modify the general properties of each log, which
specifies the output type or location of the log. Use the following
steps to adjust the properties for each log type:
- Log in to the Integrated Solutions Console:
- Open a browser and navigate to the following
URL: https://host_name:port/ibm/console.
Where:
- host_name is the fully qualified host name
of the server where the application or the network deployment manager
is deployed.
- port is the secured port used to access the
console. The default port is 9043.
Note: The default unsecured port is 9060.
If you use 9060, you must have "http" instead of "https" in the URL.
- Enter an administrator user ID and password.
- Click Log in.
- In the navigation pane, click .
Note: If you are using WebSphere® Application Server version 6.1.0.x, reach
this window by clicking .
- Click the name of the server you want to manage.
- Under Troubleshooting, click Logging and Tracing.
- Click one of the log types. Then click the Configuration
tab to make a static change to the system log configuration, or click
the Runtime tab to change the configuration dynamically.
Note: Separate
logs for each log type exist for all Java™ virtual
machines (JVMs) on a node, including all application servers and their
node agent, if present, as well as for a deployment manager in its
own logs directory.
Here is a list of the available log types:
Option |
Description |
Diagnostic Trace |
Provides information in the trace.log about
how the WebSphere Application Server components
run. |
JVM Logs |
Used to view and modify the settings for the Java Virtual Machine (JVM). The System.out log
(SystemOut.log) is used to monitor the health
of the WebSphere Application Server.
The System.err log (SystemErr.log)
contains exception stack trace information used to perform problem
analysis. |
Process Logs |
Created when redirecting the standard out and standard error
streams of a process to independent log files, the native_stdout.log and native_stderr.log,
respectively. |
IBM® Service Logs |
Also known as the activity log. Records the WebSphere Application Server messages
that are written to the System.out stream and
special messages that contain extended service information that you
can use to analyze problems. |
Change Log Detail Levels |
Controls which events are processed by Java logging,
by using log levels. You can assign logging levels to individual trace
loggers or to trace groups. (Trace loggers and groups are listed in
the topic Trace loggers.) All Presence Server logs
are located in com.ibm.presence. To view them,
you can change the package log level so that the logs will appear
in the trace file, for example com.ibm.presence.*=all or com.ibm.presence.*=fine.
|
- When you are finished making your changes, click Apply.
- Click OK.
- Click Save to save changes to the
master configuration.
- Optional: If you made a static change to the
configuration, restart the application for your changes to take effect.