Abstract
This technote describes how to work around a problem deploying large war files to a WebSphere Portal V5.0.2 system configured with an external IBM HTTP Server. The problem generates the following message: Request Entity Too Large error 413 when attempting to install a large war file.
For related information about this topic, refer to the following IBM Redbooks publication:
Document Management Using WebSphere Portal V5.0.2 and DB2 Content Manager V8.2, SG24-6349-00
Contents
Work around procedure:
- Ensure the WebSphere_Portal application server is started.
- Log in to WebSphere Portal as an administrator user (for example, wpsadmin): http://<portal_server_hostname>/wps/portal Note: Make sure that WebSphere Application Server installs Web applications as unpacked .WAR files. This is the default behavior, so you should be ok unless you intentionally changed that setting.
- Click the Administration tab. Click Portlets -> Install.
- Click Browse. Select the c:\temp\<filename>.war file and click Open. Insert the: 9081 into the URL to temporarily bi-pass the external IBM HTTP Server and then click Next.
- Work around: We found that when we used an external Web server (IBM HTTP Server), we received a Request Entity Too Large error 413 when attempting to install the <filename>.war file, which is roughly 10 MB. To work around this issue, we accessed the WebSphere Portal directly by inserting the :9081/ into the URL (for example, http://<portal_server_hostname>:9081/xxxx).
- When the Install Portlets page listing the portlets appears, click Install.
Special Notices
This material has not been submitted to any formal IBM test and is published AS IS. It has not been the subject of rigorous review. IBM assumes no responsibility for its accuracy or completeness. The use of this information or the implementation of any of these techniques is a client responsibility and depends upon the client's ability to evaluate and integrate them into the client's operational environment.