|
Problem(Abstract) |
Collecting data for problems with the IBM® WebSphere®
Application Server for problems that occur during the installation of an
application (EAR/JAR/WAR) environment. Gathering this MustGather
information before calling IBM support will help you understand the
problem and save time analyzing the data. |
|
|
|
Resolving the
problem |
 |
You can automatically collect this data using IBM Support
Assistant (ISA) Lite - a special offering that contains the data
collector component of the IBM Support Assistant Workbench.
For a full range of problem-solving features, install the IBM Support Assistant
Workbench - your support workbench for finding answers and solving
problems. The workbench contains all the data collection capability of ISA
Lite plus much more!
|
|
 |
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.
Deployment specific MustGather information
- Note the application (EAR/WAR/JAR) that is causing the problem.
- If possible, stop all WebSphere processes and clear the following
directory:
- Restart the Deployment Manager or Application Server process.
- Set the following Runtime mode trace:
- For Application Server versions 6.0 and 6.1:
- In the administrative console, navigate to Troubleshooting >
Logs and Trace > dmgr > Diagnostic Trace > Change Log
Detail Levels.
Then, select the Runtime tab.
Note: If you are in a Base environment, select server1
instead of the dmgr server. If the problem is the application is
not expanded to the installedApps directory, then also enable the traces
on the NodeAgent process as well.
- In the Change Log Detail Levels, modify existing trace string
to:
*=info:com.ibm.ws.console.app*=all:com.ibm.ws.management.*=all:com.ibm.web
sphere.management.*=all |
|
- Click Apply or OK so that the trace string is saved.
- For Application Server versions 5.0 and 5.1:
- In the administrative console, navigate to Troubleshooting >
Logs and Trace > dmgr > Diagnostic Trace
Then, select the Runtime tab.
Note: If you are running in a Base environment, select
server1 instead of the dmgr server
- In the Trace Specification field, modify existing trace string
to:
com.ibm.ws.console.app*=all=enabled:com.ibm.ws.management.*=all=ena
bled:com.ibm.websphere.management.*=all=enabled |
Click Apply or OK so that the trace string is saved.
|
- If you are using wsadmin, enable the following tracing:
- Modify the wsadmin.properties file located in the following
directory:
- Uncomment the following line:
#com.ibm.ws.scripting.traceString=com.ibm.*=all=enabled |
 |
 |
- Recreate the problem.
- Save the screen capture of administrative console if error is
displayed on console screen.
- Run the collector tool
Note: If you are running in a Network Deployment environment, run
on both Network Deployment and base. For more details, see the following
Information Center topic:
- Send the collector outputs along with the specific EAR/WAR/JAR file
that is causing the problem. Also provide a clear description of what
options are chosen during the install process (If using a script to
install the application, include it as well). Send the screen capture of
the administrative console if error is displayed on the console screen.
- Follow instructions to send
diagnostic information to IBM support.
For a listing of all technotes, downloads, and educational materials
specific to the Deploy component, search the WebSphere
Application Server support site. |
|
|
|
|