|
Problem(Abstract) |
MustGather for problems with the IBM® WebSphere®
Application Server Application Profile or Access Intent component, a
Programming Model Extension (PME) that is available in WebSphere
Application Server V5 Enterprise Edition, WebSphere Business Integration
Server Foundation V5.1, and all editions of WebSphere Application Server
V6.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.
Application Profile and Access Intent specific MustGather
information
- What is the exact version and the edition (for example: Base, Network
Deployment, Enterprise, WebSphere Business Integration Server Foundation)
of WebSphere Application Server that is installed?
- Provide a full description of the problem that you have encountered,
including the stack traces of any errors or exceptions that are occurring.
Provide any logs that contain the errors or exceptions. These can usually
be found in the following directory:
- Under what circumstances does the problem occur? Does it occur every
time a certain task is done or does it occur intermittently? Has this
problem always occurred? If not, was a change recently made before the
problem started to occur?
- Send the SystemOut.log file for the application server on
which the Application Profile or Access Intent problem occurs:
- For version 6.1 and 6.0, the SystemOut.log file
is located in the following directory:
install_root/profiles/profile_name/logs/server_name |
|
- For version 5.1 and 5.0, the SystemOut.log file
is located in the following directory:
install_root/logs/server_name |
|
- Enable tracing:
- For version 6.1 and 6.0:
- In the WebSphere Application Server Administrative Console, expand
Troubleshooting and select Logs and Trace.
- In the Logging and Tracing page, select your server and then
Diagnostic Trace.
- Ensure that Enable Log is selected.
- Under Trace Output, select File, and accept the
defaults.
- Click OK and save your configuration
- Again expand Troubleshooting and select Logs and Trace.
- In the Logging and Tracing page, select your server and then
Change Log Detail Levels.
- Enter the following trace string:
*=info:AppProfile*=all=enabled:Transaction=all=enabled |
|
- Click OK and save your configuration.
- Restart the Application Server.
- Re-create the problem.
- Send the resulting trace output file.
- For version 5.1 and 5.0:
- In the WebSphere Application Server Administrative Console, expand
Troubleshooting and select Logs and Trace.
- In the Logging and Tracing page, select your server and then
Diagnostic Trace.
- Ensure that Enable trace with the following specification is
selected.
- In the Trace Specification field, enter the following trace
string:
*=info:AppProfile*=all=enabled:Transaction=all=enabled |
|
- Under Trace Output, select File, and accept the
defaults.
- Click OK and save your configuration.
- Restart the Application Server.
- Re-create the problem.
- Send the resulting trace output file.
- Run
the collector tool to produce a JAR file containing your Application
Server configuration files and other logs that are useful to the WebSphere
Application Server support team.
- Follow instructions to send
the following diagnostic information to IBM support:
- The SystemOut.log file.
- The trace output file.
- The collector output.
For a listing of all technotes, downloads, and educational materials
specific to Application Profile and Access Intent, search the following
support sites:
|
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|