InfoCenter Home > 6.6.8: Administering Web modules (overview)Classpath considerationsAn important classpath-related setting to note is the Module Visibility. This application server setting impacts the portability of applications and standalone modules from other WebSphere Application Server versions and editions. If your existing module does not run as-is when you transfer it to Version 4.0, you might need to reassemble an existing module or change the module visibility setting. See the information on setting classpaths for a full discussion of classpath considerations. See the application server property reference for information about the module visibility setting. Identifying a welcome page for the Web applicationThe default welcome page for your Web application is assumed to be named index.html. For example, if you have an application with a Web path of: /webapp/myappthen the default page named index.html can be implicitly accessed using the following URL: http://hostname/webapp/myapp To identify a different welcome page, modify the properties of the Web module when you are assembling it. See the article about assembling Web modules with the Application Assembly Tool (article 6.6.8.5). Web application URLs are now case-sensitive on all operating systems
For example, suppose you have a Web client application that runs successfully on Version 3.5.x. When running the same application on Version 4.0, you encounter an error that the welcome page (typically index.html), or HTML files to which it refers, cannot be found: Error 404: File not found: Banner.html Error 404: File not found: HomeContent.html Suppose the content of the index page is as follows: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.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>but the actual file names in \WebSphere\AppServer\installedApps\... directory in which the application is deployed are: banner.html homecontent.html To correct the 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. |
| ||
|