This section explains how you can configure a Web server to communicate with IBM® Lotus® Quickr™ for WebSphere Portal.
Using a web server is required for production deployments of Lotus Quickr. Avoid directly accessing the HTTP transport of IBM WebSphere® Application Server. Cache header and gzip compression configuration are done in the web server. Without cache header configuration, performance can be severely degraded, and gzip compression in the web server is recommended for resources that are not already compressed. Maintenance pages can be configured in your web server as well. Refer to your web server documentation for configuring cache headers, gzip compression and configuring redirects for error or maintenance pages.
Accessing the server through HTTP: qp85
By default IBM Lotus Quickr for WebSphere Portal uses the internal HTTP transport within IBM WebSphere Application Server to handle requests. WebSphere Application Server also supports the use of an external Web server, so that you can access Lotus Quickr from your Web server.
Setting up a Web server with Lotus Quickr: qp85
Set up your Web server to communicate with IBM Lotus Quickr for WebSphere Portal by installing and configuring the Web server plug-in provided by IBM WebSphere Application Server.
Recommended HTTP Server configuration: qp85
Over a wide-area network, latencies can be significant, and bandwidth limited. In this case, the time to transfer the page content from the server to the client can become a significant contributor to overall page response time.
Parent topic: Configuring: qp85