f you have already contacted support, continue on to the
component's specific MustGather information. Otherwise, click: MustGather:
Read First for all WebSphere Application Server Products.
Enterprise Application and Application Assembly Tool (AAT) specific
MustGather:
- Detailed explanation of at what point the problem is occurring
(opening in AAT, code generation, installation into Application Server,
after installation, verification in AAT, etc)
- The complete file that is being opened/installed (.ear, .war,
.jar).
- How was the file created/developed (VisualAge® for Java™ if so which
version, WebSphere Studio Application Developer, AAT, ANT scripting,
etc)
- If the customer is having problems with an ear file, is the problem
with one of the modules within the ear file or does the problem occur once
they are packaged into the ear.
- Have customer run verify on the module (ear, war, ejb, client) in the
AAT by hitting the verify button. This, among other things, will verify
that the module is up to J2EE standard. If errors occur capture in a
screen shot or cut and paste into a text document.
- If the ear is having a problem after being installed, what are the
classloader settings?
- Has this application ever been installed and worked on Application
Server previously? If so what version?
- Are there any error messages?
Note: There is NO logging for the AAT
besides that printed to the screen in the message field of the code
generation window or in pop up error messages. Gather these messages thru
screen shots or cut and paste into a text document.
Follow instructions to send
diagnostic information to IBM support.
For a listing of all technotes, downloads, and educational materials
specific to the component, search the WebSphere
Application Server support site.
|