Web application deployment troubleshooting tips

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.

Web module migrated from version 4.x does not run in later WebSphere Application Server version.

Note: 이 주제는 하나 이상의 애플리케이션 서버 로그 파일을 참조합니다. 권장되는 대안은 분배 및 IBM® i 시스템에서 SystemOut.log, SystemErr.log, trace.logactivity.log 파일을 사용하는 대신 HPEL(High Performance Extensible Logging) 로그를 사용하고 인프라를 추적하도록 서버를 구성하는 것입니다. 원시 z/OS® 로깅 기능과 연계하여 HPEL을 사용할 수도 있습니다. HPEL을 사용하는 경우 서버 프로파일 바이너리 디렉토리의 LogViewer 명령행 도구를 사용하여 모든 로그에 액세스하고 정보를 추적할 수 있습니다. HPEL 사용에 대한 자세한 정보는 HPEL을 사용한 애플리케이션 문제점 해결 정보를 참조하십시오.
Symptom Problem Recommended response
Your version 4.x web module does not run when you migrate it to Version 8.0 or later products. In version 4.x, the classpath setting that affected visibility was Module Visibility Mode. In versions 6.0 and later, you must use class loader policies to set visibility. 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.

Welcome page is not visible.

Symptom Problem Recommended response
You cannot access an application with a web path of:
  /webapp/myapp
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.

To identify a different welcome page, modify the properties of the web module during assembly. See the article, Assembling web applications, for more information.

HTML files are not found.

Symptom Problem Recommended response
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
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
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.

Proxy server cannot access a Web module

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.

우수 사례 우수 사례: You should use a different context root for the Web module in each application, or use an application server instead of a proxy server to access the Web module.bprac

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.


주제 유형을 표시하는 아이콘 참조 주제



시간소인 아이콘 마지막 업데이트 날짜: July 9, 2016 6:09
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=rweb_deployt
파일 이름:rweb_deployt.html