ESI vars Tag ESI Tag Descriptions

11-52 Oracle Fusion Middleware Administrators Guide for Oracle Web Cache 12 Caching with Third-Party Application Servers 12-1 12 Caching with Third-Party Application Servers This chapter discusses how to configure Oracle Web Cache with third-party application Web servers. This chapter includes the following topics: ■ Section 12.1, Introduction to Third-Party Application Servers ■ Section 12.2, IBM WebSphere ■ Section 12.3, Apache Tomcat ■ Section 12.4, Microsoft IIS

12.1 Introduction to Third-Party Application Servers

Because Oracle Web Cache is transparent to the application Web server, the application Web server treats HTTP requests from Oracle Web Cache as any other HTTP request coming directly from the browser. In turn, the application Web server generates the response and sends it back to Oracle Web Cache as an HTTP message. Because Oracle Web Cache fully supports HTTP, it can work with any HTTP-compliant application Web server. How the application Web servers choose to generate HTTP responses is irrelevant to Oracle Web Cache. The type of application Web server that a site uses depends mainly on the types of applications that site is running. For example, if customers want to run Active Server Pages ASP, then they may prefer to use Microsoft Internet Information Server IIS as the application Web server. ■ Section 12.1.1, Web Site Configuration ■ Section 12.1.2, Caching Rules and Expiration Rules Notes: ■ While this chapter describes how Oracle Web Cache works with three specific kinds of servers, Oracle Web Cache works with any HTTP-compliant application Web server. ■ The application examples used in the discussions of these third-party servers are relatively simple. Running with production applications requires more extensive configuration of Oracle Web Cache. Refer to the third-party application Web server documentation for information about designing applications. 12-2 Oracle Fusion Middleware Administrators Guide for Oracle Web Cache

12.1.1 Web Site Configuration

You configure Oracle Web Cache to communicate with a third-party application Web server the same way you do with Oracle HTTP Server, by providing the host name and the listening port number. Table 12–1 shows the default values for the listening ports for the products discussed in this appendix. To configure Oracle Web Cache to communicate with a third-party application Web server, perform the following tasks: 1. See Section 2.11.1 to change Oracle Web Cache port settings 2. See Section 2.11.2 configure application Web server settings 3. See Section 2.11.3 and Section 2.11.4 configure Web site settings

12.1.2 Caching Rules and Expiration Rules

You assign caching rules and expiration rules when using third-party application Web servers in the same way as when using Oracle HTTP Server. You can choose to cache or not to cache content for the following: ■ Static objects ■ Multiple-version objects for the same URL ■ Pages supporting a session cookie or embedded URL parameter ■ Pages containing simple personalization ■ Dynamic assembly of Edge Side Includes ESI fragments You can also assign an expiration time limit to objects or invalidate objects at any time. See Chapter 6, Caching and Compressing Content, and Chapter 7, Invalidating Content.

12.2 IBM WebSphere

When Oracle Web Cache fetches static content from IBM Websphere Application server, the IBM Websphere Application Server sends a content=ESI1.0+ directive in the Surrogate-Control response header in the response to the Oracle Web Cache Surrogate-Capability: orcl=ESI1.0 request. Oracle Web Cache ignores the ESI1.0+ features to get rid of page rendering issues and errors. If Oracle Web Cache is deployed as a caching solution, this difference in the control directive value may result in undefined Web application behavior. Follow these steps to force IBM Websphere Application Server to send ESI1.0 instead of ESI1.0 or later:

1. In the WebSphere Application Server administrative console, navigate to Servers

Application servers. The Application servers page appears. Table 12–1 Third-Party Application Web Server Default Listening Ports Application Web Server Port IBM WebSphere Application Server, Version 6.0 80 Apache Tomcat, Version 4.1 8080 Microsoft IIS 6.0 80