|
Question |
MustGather for Web services security problems with IBM®
WebSphere® Application Server. Gathering this information before calling
IBM® support will help familiarize you with the troubleshooting process
and save you time. |
|
|
|
Answer |
If you have already contacted support, continue on to the
component-specific MustGather information. Otherwise, click: MustGather:
Read first for all WebSphere Application Server products.
Web services security specific MustGather
It can be very difficult determining the root cause of a Web service
security problem. In order to help problem determination, submit
the following:
- A clear, specific problem description, including specific usage
information and error scenario.
- Web service security traces:
- To get these, run a trace on the application server where the Web
service is located. Use the following trace string:
com.ibm.ws.webservices.wssecurity.*=all=enabled
com.ibm.xml.*=all=enabled
com.ibm.wsspi.wssecurity.*=all=enabled
com.ibm.wsspi.webservices.*=all=enabled |
Enter the preceding trace string in the Administrative Console:
Servers > Application Servers > server_name >
Diagnostic Trace Service > Trace Specification
|
- Clear out the files, SystemOut.log and trace.log, in the
install_root/logs directory for the server.
- Stop and restart the server.
- Recreate the problem.
- Submit
the SystemOut.log and trace.log files.
- A simple and deployable testcase, with specific instructions on how to
recreate the problem you encountered.
- Follow instructions to send
diagnostic information to IBM support.
For a listing of all technotes, downloads, and educational materials
specific to the Web services component, search the WebSphere
Application Server support site. |
|
|
|