If you are not able to display a resource in your browser, follow these steps:
If you cannot access the resource directly through the Application Server, Verify that the URL used to access the resource is correct.
If the URL is incorrect and it is created as a link from another JSP file, servlet, or HTML file, try correcting it in the browser URL field and reloading, to confirm that the problem is a malformed URL. Correct the URL in the "from" HTML file, servlet or jsp file.
If the URL appears to be correct, but you cannot access the resource directly through the Application Server, verify the health of the hosting Application Server and Web module:
http://hostname/myapp/servlet/com.mycom.welcomeServlet
Diagnosing Web server problems
If you are unable to view the welcome page of your HTTP server, determine if the server is operating properly.
On Windows systems, look in the Services panel for the service corresponding to your HTTP server, and verify that the state is Started. If not, start it. If the service does not start, try starting it manually from the command prompt. If you are using IBM HTTP Server, the command is IHS_install_dir\apache .
On UNIX systems, execute the ps -ef | grep httpd command. There should be several processes running with a name of "httpd". If not, start your HTTP server manually. If you are using IBM HTTP Server, the command is IHS_install_dir/bin/apachectl start.
If the HTTP server does not start:
Accessing a Web resource through the application server and bypassing the HTTP server
Starting with WebSphere Application Server Version 4.0, you can bypass the HTTP server and access a web resource through the application server. It is not recommended to serve a production Web site in this way, but it provides a good diagnostic tool when it is not clear whether a problem resides in the HTTP server, WebSphere Application Server, or the HTTP plug-in.
To access a Web resource through the Application Server: