Troubleshoot: Access Web resources
When you are unable to access a Web resource from your browser, you use different resources to determine what the problem is, depending on the nature of the problem occurring. For information about which resources to use, see the list of resources below.
Unable to serve any Web resources
See the Installation of WebSphere Application Server for iSeries topic. Steps 3, 4, and 5 of that document guide you through the system verification and serving of a web resource. To ensure that your application server and Web server are configured correctly and have been started, read the information in steps 3, 4, and 5.
If you are using IBM HTTP Server (powered by Apache) for your Web server, generate a trace of your HTTP server instance and look for errors. For information on tracing an IBM HTTP Server instance, see the Trace the IBM HTTP Server instance topic in.
Web server plugin trace. For information on tracing the WebSphere Application Server Web server plugin, see Tracing the Web server plugin.
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.
Unable to serve a particular web resource
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.
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.IBM support services. For more information, see Get support for WebSphere Application Server.
Servlet or JSP displays an error or Java exception instead of the expected output
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. For more information, see the Add logging and tracing to your application topic in Programming.
Add output to your servlet, JSP, or 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 servlet or Java class in which the error is occurring.
If the failure is occurring within a JSP, use the keepgenerated attribute to keep the generated servlet source file to inspect for problems.
Web server plugin trace. For information on tracing the WebSphere Application Server Web server plugin, see Tracing the Web server plugin.
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.IBM support services. For more information, see Get support for WebSphere Application Server.