Troubleshoot: Application Assembly Tool

If you are having problems starting or using the WebSphere Application Server Application Assembly Tool (AAT), perform these steps:

• Enable the printing of messages and exceptions to the screen.
  • Modify the assembly.bat or assembly.sh file located in the bin directory of the product installation. Change the statement "start javaw" to just "java".
  • Restart the AAT and the command window is displayed through the lifetime of the Java process and displays messages and exceptions.

  • Look up any error or warning messages you see in the message reference link to message reference section.

• With a problem application open in the AAT, use the Verify menu command. This command goes through all components of the application and validates them for any XML errors or invalid entries such as missing fields, or invalid bean or class references.

• To verify the integrity of an EAR (Enterprise Archive) file, expand it manually (outside of the AAT) by running the EARExpander script and supplying the name of the EAR file as a parameter. For more information on the EARExpander script, see the The EARExpander script topic in Administration. Browse the directory structure of the expanded EAR file to see if it contains all the expected files.

• Ensure that the enterprise application complies with J2EE specification level 1.3 and that any enterprise beans it contains conform to the EJB 1.1 or 2.0 Specification level.

• Read the release notes. WebSphere Application Server Release Notes (http://publib.boulder.ibm.com/was400/docs/relnotes502.html) .

• Check the WebSphere Application Server FAQ database .

• Refer to the WebSphere Application Server for iSeries newsgroup .
  This iSeries Technical Support Web-based forum is dedicated to WebSphere Application Server for iSeries.

• Contact IBM support. For more information, see Get support for WebSphere Application Server.