Web app deployment troubleshooting tips


 

+

Search Tips   |   Advanced Search

Deployment of a Web app is successful if we can access the application by typing a URL in a browser or if we can access the application by following a link. If we cannot access the application, follow these steps to eliminate some common errors that can occur during migration or deployment.

 

Web module does not run in WAS V 5.x or 6.x

Symptom Your Web module does not run when you migrate it to V5.x or 6.x
Problem In V4.x, the classpath setting that affected visibility was Module Visibility Mode. In Vs 5.x and 6.x, use class loader policies to set visibility.
Recommendation Reassemble an existing module, or change the visibility settings in the class loader policies.

See...

 

Web module does not run in WAS V 6.1

Symptom Your Web module does not run when you migrate it to V6.1.
Problem In V4.x, the classpath setting that affected visibility was Module Visibility Mode. In V6.1, use class loader policies to set visibility.
Recommendation Reassemble an existing module, or change the visibility settings in the class loader policies.

 

Welcome page is not visible.

Symptom We cannot access an application with a Web path of: 

  /webapp/myapp
Problem The default welcome page for a Web app is assumed to be IBM_HTTP_Server_v735.html. We cannot access the default page of the myapp application unless it is named IBM_HTTP_Server_v735.html.
Recommendation To identify a different welcome page, modify the properties of the Web module during assembly.

 

HTML files are not found.

Symptom Your Web app ran successfully on prior versions, but now you encounter errors that the welcome page (typically IBM_HTTP_Server_v735.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 app 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
Recommendation To correct this problem, modify the IBM_HTTP_Server_v735.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.

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.


Related concepts

Class loaders

 

Related tasks

Diagnose problems (using diagnosis tools)
Task overview: Securing resources

 

Related

Web apps: Links