|
Problem(Abstract) |
Collecting data for WSIF problems with the IBM® WebSphere®
Application Server Web services component. Gathering this MustGather
information before calling IBM support will help you understand the
problem and save time analyzing the data. |
|
|
|
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.
WSIF specific MustGather information:
- What is your environment (client and server platform, software)?
- Description of your problem, including any errors.
- Description of the steps taken to reproduce your problem, if it can be
recreated.
- What is your WSIF version? (see Section A below)
- Provide a trace demonstrating your problem. (see Section B below)
- Provide a trace for any other relevant components.
- Provide the Web Services Definition Language (WSDL) and schema files
you are using.
- What level of wsdl4j.jar are you using? (see Section C
below)
- If you have your own provider or a correlation service, give
details.
- If altered, provide your wsif.properties file.
- If you are using Java™ Message Service (JMS) or Java Naming and
Directory Interface™ (JNDI), give details of your setup.
- If you have reimplemented the mapping conventions class, provide
details.
- Provide a list of all fixes that you have applied.
- Provide a TCPMON trace, if possible. (see Section D below)
- What transport are you using?
- If possible, provide source code or a simple test case that
demonstrates your problem.
Sections:
- For the WSIF version, find the size and date of your wsif.jar
and the location from where you obtained wsif.jar.
- To switch the trace on, if running inside Application Server:
org.apache.wsif.*=all=enabled:com.ibm.wsif.*=all=enabled |
|
If running stand-alone, in your log4j.properties
specify the following settings to trace to wsif.log: |
|
log4j.rootCategory=INFO, CONSOLE,
LOGFILE
log4j.logger.org.apache.wsif.*=DEBUG
log4j.logger.com.ibm.wsif.*=DEBUG
log4j.appender.LOGFILE=org.apache.log4j.FileAppender
log4j.appender.LOGFILE.File=wsif.log
log4j.appender.LOGFILE.Append=true
log4j.appender.LOGFILE.Threshold=DEBUG |
|
WSIF uses Apache commons-logging for its messages and
trace. See http://jakarta.apache.org/commons/logging
for more information. Commons-logging is an API that wraps various log
implementations. You can configure commons-logging to use other log
implementations, or even your own. So commons-logging.jar must be
on the classpath, and log4j is the default log implementation, although
commons-logging.jar contains other log implementations. You can
configure commons-logging.properties to use a different log
implementation. If using log4j, you configure log4j.properties to
redirect trace and switch it on. The log4j.properties settings
above are only a subset of all possibilities.
For further information at http://ws.apache.org/wsif/developers/trace.html |
|
- To find the level of the wsdl4j.jar, check the
Manifest.mf file within the .jar file, where a Application Server
version number is located.
- To obtain a TCPMON trace, follow these instructions
http://publib.boulder.ibm.com/infocenter/wasinfo/v5r1//index.jsp?topic=/com.ibm.websphere.exp.doc/info/exp/ae/twbs_tracewbs.html
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. |
|
|
|