Deployment of a Web application is successful if you can access the application by typing a Uniform Resource Locator (URL) in a browser or if you can access the application by following a link. If you cannot access your application, follow these steps to eliminate some common errors that can occur during migration or deployment.
Symptom | Your version 4.x Web module does not run when you migrate it to version 5.0 or later products. |
Problem | In version 4.x, the classpath setting that affected visibility was Module Visibility Mode. In versions 5.0 and later, you must use class loader policies to set visibility. |
Recommended response | Reassemble an existing module, or change the visibility settings
in the class loader policies. Refer to the Class loaders and Class loading articles for more information. |
Symptom | You cannot access an application with a Web path of: /webapp/myapp |
Problem | The default welcome page for a Web application is assumed to be index.html. You cannot access the default page of the myapp application unless it is named index.html. |
Recommended response | To identify a different welcome page, modify the properties of the Web module during assembly. See the article, Assembling Web applications, for more information. |
Symptom | Your Web application ran successfully on prior versions,
but now you encounter errors that the welcome page (typically index.html),
or referenced HTML files are not found: Error 404: File not found: Banner.html Error 404: File not found: HomeContent.html |
Problem | For security and consistency reasons, Web application URLs
are now case-sensitive on all operating systems. Suppose the content of the index page is as follows: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 5.0 Frameset//EN"> <HTML> <TITLE> Insurance Home Page </TITLE> <frameset rows="18,80"> <frame src="Banner.html" name="BannerFrame" SCROLLING=NO> <frame src="HomeContent.html" name="HomeContentFrame"> </frameset> </HTML> However the actual file names in the \WebSphere\AppServer\installedApps\... directory where the application is deployed are: banner.html homecontent.html |
Recommended response | To correct this problem, modify the index.html file to change the names Banner.html and HomeContent.html to banner.html and homecontent.html to match the names of the files in the deployed application. |
If you use the same context root when you install two applications that have the same Web module, and one of the applications is disabled. you are not able to use a proxy server to access the Web module. When this situation occurs, a 503 Service Unavailable error message is recoreded in the SystemOut and SystemErr logs.
For current information available from IBM® Support on known problems and their resolution, see the IBM Support page.
IBM Support has documents that can save you time gathering information needed to resolve this problem. Before opening a PMR, see the IBM Support page.