|
Problem(Abstract) |
Collecting data for Web services gateway problems in
WebSphere® Application Server V6.0, 5.1, and 5.0. Gathering this
information before calling IBM® support will help familiarize you with the
troubleshooting process and save you time. |
|
|
|
Resolving the
problem |
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 gateway specific MustGather information
- Identification of your environment - client and server platform and
software.
- Description of your problem, including any errors.
- Description of the steps taken to reproduce your problem, if the
problem can be recreated.
- Identification of your gateway version (see Section A. below).
- Identification of the WebSphere Application Server version (V6.0, 5.1,
or 5.0).
- The size and date of the following JAR files, located in your
install_root/lib directory:
- wsif.jar
- wsdl4j.jar
- qname.jar
- activation.jar
- jrom.jar
- mail.jar
- soap.jar (in the
installedApps/node_name/wsgw.ear
file)
- uddi4j.jar
- Do you have an axis.jar file in the
install_root/lib directory?
- A list of all the fixes that you have applied.
- The TCPMON trace - requests and responses, both into and out of the
gateway (see Section B. below).
- The WebSphere Application Server trace - immediately before and
immediately after the failure (see Section B. below).
- The following logs:
- SystemOut.log
- SystemErr.log
- trace.log
- Identification of the transport that is used by your client and your
target service (for example: Axis, Apache soap)
- A screen capture of service development (see Section C. below).
- A screen capture of any Web services gateway administrative tool
graphical user interface errors.
- The text of the gateway Web Services Definition Language (WSDL) and
the target WSDL.
- Identification of any generic or deployed classes (on gateway service
deployment).
- The source code, if a problem exists with a filter or exception
handler.
- The database (for example: DB2®, Cloudscape™) and version that you are
using.
- Follow instructions to send
diagnostic information to IBM support.
Sections:
- To find your gateway version, select about on the main
administrative panel.
- To identify the trace string to use for gateway tracing:
- For WebSphere Application Server V6.0:
com.ibm.ws.webservices.*=all=enabled
:com.ibm.ws.sib.*=all=enabled
:org.apache.wsif.*=all=enabled |
|
- For WebSphere Application Server V5.1 and V5.0:
com.ibm.wsgw.*=all=enabled
:org.apache.wsif.*=all=enabled |
|
The tcpmon utility is found in the org.apache.axis.utils
package (within the
axis.jar file) and provides an invaluable method of monitoring
the contents of Network Deployment response messages. To use this utility,
you must modify your target destination to a different port value on the
local machine on which the tcpmon utility can listen. Having
intercepted each request or response message, the tcpmon utility
then forwards the message on to its correct destination.
To run the tcpmon utility, enter the following from the command
line:
java -cp
YourAxisJarClassPath/axis.jar org.apache.axis.utils.tcpmon
[TcpmonListenPort targetHost targetPort] |
|
For example:
java -cp
YourAxisJarClassPath/axis.jar org.apache.axis.utils.tcpmon 8091
TargetHostName.uk.ibm.com 80 |
|
|
- To obtain a screen capture of service deployment, go to the main
administrative panel, select services list > required
service.
For a listing of all technotes, downloads, and educational materials
specific to the Web services gateway, search the WebSphere
Application Server support site. |
|
|
|