From the WebSphere® Application
Server administrative
console, you can enable or disable trace logging, change the log file
location, size and retention, and modify the log entry format.
About this task
These settings apply to all applications that use Apache
Commons Logging standard. It is not usually necessary to change these
settings when troubleshooting IBM CMIS for Content Manager
OnDemand
To
ensure that log data is retained properly, you can specify the maximum
file size and maximum number of historical files. However, be sure
to account for the log level that is configured and the load that
the configuration will place on your system.
By
default, the SystemOut.log and the trace.log files
are located in the WAS_profile_location/logs/server subdirectory
of the WebSphere Application
Server installation
directory. For example, on a standard AIX installation, the log files
would be in the /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/server1/ directory.
Procedure
To configure logging for IBM ECM CMIS:
-
Log in to the WebSphere Application
Server administrative console
and expand Troubleshooting.
-
Click Logs and trace,
and then click the name of the server where IBM CMIS for Content Manager
OnDemand is installed.
-
To configure SystemOut.log, click JVM
logs in the Logging and Tracing panel.
Specify the logging output for your configuration on the appropriate
tab for your environment:
- Configuration
By default, the Configuration tab
is active. Any changes that you make on the Configuration tab
are saved to the WebSphere Application
Server configuration
files, but your changes are not activated until you restart the server.
- Runtime
This option is recommended. Any changes that you make to the logging level on the
Runtime tab are activated immediately.
Tip: If the
Runtime tab is active and you want to make your changes permanent, select
Save runtime changes to
configuration.
-
Click Apply.
-
To configure trace.log, click Diagnostic
Trace in the Logging and Tracing panel.
Specify the trace output for your configuration on the appropriate
tab for your environment:
- Configuration
By default, the Configuration tab
is active. Any changes that you make on the Configuration tab
are saved to the WebSphere Application
Server configuration
files, but your changes are not activated until you restart the server.
- Runtime
This option is recommended. Any changes that you make to the logging level on the
Runtime tab are activated immediately.
Tip: If the
Runtime tab is active and you want to make your changes permanent, select
Save runtime changes to
configuration.
-
Click Apply.