|
Problem(Abstract) |
Step by step instructions for obtaining a security trace
on WebSphere® Application Server V5 releases. |
|
|
|
Cause |
A security trace is very valuable for troubleshooting
authentication problems. This technote explains how to enable a security
trace using either by using the trace string or by selecting the trace
options in the WebSphere Application Server administrative console. |
|
|
Resolving the
problem |
Perform the following steps to obtain a security trace in
V5 releases:
- Log in to the WebSphere Application Server administrative console.
- Navigate to Servers > Application >Servers >Server1.
- Open Server1 and go to Diagnostic Trace Service.
In the Trace Specification field, the default is
*=all=disabled.
Type the following string (you can cut and paste from this document):
com.ibm.ws.security.*=all=enabled:com.ibm.ws.security.core.SecurityDM=all=disabled:com.ibm.ws.security.policy.NullDynamicPolicy=all=disabled:
OR
Perform the following steps:
- For the Trace Specification, click Modify....
- On the window that opens, select the Components tab.
- Click the + sign beside com.ibm.ws.* to expand
listing.
 com.ibm.ws.*
- Click the com.ibm.ws.security.* link and select
All enabled.
 com.ibm.ws.security.*
- Click the + sign beside com.ibm.ws.security.* to
expand listing.
- Select following links and select all disabled.
com.ibm.ws.security.core.SecurityDM
com.ibm.ws.security.policy.NullDynamicPolicy
- Click Apply, then Close.
The traces are captured in the file specified in the Trace Output :
File Name field.
Default is ${SERVER_LOG_ROOT}/trace.log |
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|