Troubleshoot: Enterprise applications

Use the resources listed below to determine the cause of problems that occur when running your application code within WebSphere Application Server.

• Check Troubleshooting guide for the J2EE application client
  This topic describes debugging tips for resolving several J2EE application client problems.

• Check the application server standard output and standard error log files for errors. For information on the application server log files and where they are located, see WebSphere Application Server log files.

• Add logging and tracing to your application using the JRas framework. See Add logging and tracing in the Application Development topic for more information.

• Add output to your enterprise bean or other Java code in the form of System.out.println() statements to aid in debugging. The output from any System.out.println() statements is written to the standard output log file for the application server in which the code is running. For information on the application server log files and where they are located, see WebSphere Application Server log files.

• Use one of the debugger tools available for debugging WebSphere Application Server for iSeries to step into the Java code in which the error is occurring. For more information, see the Debugger tools topic in Programming.

• 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.