Oracle® Application Server 10g Upgrading from Release 1 (1.0.2.2.x) to 10g (9.0.4)
10g (9.0.4) Part No. B13674-02 |
|
![]() |
![]() |
This chapter contains step-by-step instructions for upgrading Oracle9iAS Web Cache. It contains the following sections:
An upgrade item is an aspect of configuration that is acted upon during upgrade: a file, executable, or a setting that you must add, change, or delete/replace in the 10g (9.0.4) installation. Oracle Application Server Web Cache upgrade items are described in Table 4-1.
Table 4-1 OracleAS Web Cache Upgrade Items
OracleAS Web Cache works in concert with Oracle HTTP Server and Oracle Application Server Portal to receive and process requests to the application server. These components must be provided with certain host name and port values in order to function together. Specifically:
OracleAS Web Cache needs to access the origin servers. To do this, it must be provided with the Oracle HTTP Server host name and port.
OracleAS Portal must be provided with the OracleAS Web Cache host name, listening port, and invalidation port.
For information about the relationship between Oracle HTTP Server port values and OracleAS Web Cache port values, see Section 2.2.2, "Oracle Application Server Web Cache".
This section provides instructions for upgrading each item identified in Section 4.1, "OracleAS Web Cache Upgrade Items". It is divided into the following subsections:
The OracleAS Web Cache component is not automatically configured by the installation unless the Web Cache component was selected during installation.
If Web Cache was not selected during installation and the configuration steps below were not performed after the installation, Web Cache will not appear in the list of components in the System Components page Oracle Enterprise Manager 10g. In that case, you must configure it before upgrading by performing the following steps:
Start the Oracle Application Server 10g (9.0.4) instance and access the Oracle Enterprise Manager Application Server Control home page. Use the Oracle Enterprise Manager Application Server Control to configure OracleAS Web Cache:
On the System Components page, click Configure Component.
On the resulting page, select Web Cache from the drop-down list and click Continue.
A progress message appears as OracleAS Web Cache is configured, then the message "Component Web Cache has been configured."
Click OK.
The System Components page reappears. Web Cache now appears in the list of components. The default configuration, set during installation, is in effect.
From the The Oracle Enterprise Manager Application Server Control, you can access the Web Cache Manager, the graphical user interface provided for editing the configuration stored in the webcache.xml
file. Follow these steps to access the Web Cache Manager from the System Components page:
In the Administration section, click the Web Cache Administration link.
The Web Cache Administrator password dialog appears.
Enter the ias_admin
password.
The Web Cache Manager page appears. A scrollable frame on the left side of the window contains groups of configuration elements. To access an element, click on its link. The content area of the page is then populated with the values for that element.
Follow these steps to upgrade the administration, invalidation, statistics, and listen ports.
Open the webcache.xml
file in the Oracle9iAS Release 2 (1.0.2.2.x) Oracle home.
Locate the values for the administration, invalidation, and statistics ports in the Release 2 (1.0.2.2.x) webcache.xml
file.
In the Web Cache Manager page frame, locate the Ports section in the frame and click the Operations Ports link.
The content area is populated with the available caches.
Select the radio button for the cache you want and click Edit Selected.
The Edit Operations Ports window opens.
Set the ADMINISTRATION port number to the value specified in the Oracle9iAS Release 2 (1.0.2.2.x) webcache.xml
file.
Set the INVALIDATION port number to the value specified in the Oracle9iAS Release 2 (1.0.2.2.x) webcache.xml
file.
Set the STATISTICS port number to the value specified in the Oracle9iAS Release 2 (1.0.2.2.x) webcache.xml
file.
Click Submit.
The Web Cache Manager page reappears.
Click Apply Changes.
The page refreshes with a message to restart Web Cache.
Click Restart.
Locate the Ports section in the frame and click Listen Ports.
The Listen Ports page appears.
Select the radio button for the cache you want and click Edit Selected.
The Edit/Add Listen Port window opens.
Set the LISTEN port number to the value specified in the Oracle9iAS Release 2 (1.0.2.2.x) webcache.xml
file.
Click Submit.
The Web Cache Manager page reappears.
Click Apply Changes.
The page refreshes with a message to restart Web Cache.
Click Restart.
A dialog box opens with a message that the cache was stopped and started.
Click OK.
Follow these steps to upgrade the rules for cacheability, session caching, expiration, and multi-version cookies.
Open the webcache.xml
file in the Oracle9iAS Release 2 (1.0.2.2.x) Oracle home.
Locate the rules in the Release 2 (1.0.2.2.x) webcache.xml
file.
In the Web Cache Manager page frame, locate the Rules for Caching, Personalization, and Compression section in the frame and click the Caching, Personalization, and Compression Rules link.
The content area is populated with the available caching rules.
Select the radio button for the cache you want and click Edit Selected.
The Edit/Add Caching, Personalization, and Compression Rule window opens.
Enter the values and click Submit.
The Web Cache Manager page reappears.
Click Apply Changes.
The page refreshes with a message to restart Web Cache.
Click Restart.
In the Web Cache Manager page frame, locate the Rules for Caching, Personalization, and Compression section in the frame and click the Session Definitions link.
The content area is populated with the session definitions for the current site.
Select the site you want to configure from the drop-down list.
Select the radio button for the session you want and click Edit Selected, or click Add to add a session.
The Edit/Add Session Definition window opens.
Edit or add the values for the session and click Submit.
The Web Cache Manager page reappears.
Click Apply Changes.
The page refreshes with a message to restart Web Cache.
Click Restart.
A dialog box opens with a message that the cache was stopped and started.
Click OK.
To upgrade additional sessions, click the Session Definitions link to populate the content area with caches again, and repeat Steps 4 through 13.
Follow these steps to create hosts for the application web servers used in Oracle9iAS Release 2 (1.0.2.2.x).
Open the webcache.xml
file in the Oracle9iAS Release 2 (1.0.2.2.x) Oracle home.
Locate the host definitions in the Release 2 (1.0.2.2.x) webcache.xml
file.
In the Web Cache Manager page frame, locate the Origin Servers, Sites and Load Balancing section in the frame and click the Origin Servers link.
The content area is populated with the current application server hosts.
Click Add.
The Add Application Web Server window opens.
Enter the values and click Submit.
The Web Cache Manager page reappears.
Click Apply Changes.
The page refreshes with a message to restart Web Cache.
Click Restart.
To add additional hosts, click the Origin Servers link and repeat Steps 4 through 9.
Follow these steps to create site-to-server mappings for forwarding of requests to application server hosts.
Open the webcache.xml
file in the Oracle9iAS Release 2 (1.0.2.2.x) Oracle home.
Locate the site-to-server mappings in the Release 2 (1.0.2.2.x) webcache.xml
file.
In the Web Cache Manager page frame, locate the Origin Servers, Sites and Load Balancing section in the frame and click the Site-to-Server Mapping link.
The content area is populated with the current site and origin server pairs.
Select the radio button for the site and server you want and click Edit Selected, or click Add to add a session.
The Edit/Add Site-to-Server Mapping window opens.
Edit or add the values for the session and click Submit.
The Web Cache Manager page reappears.
Click Apply Changes.
The page refreshes with a message to restart Web Cache.
Click Restart.
A dialog box opens with a message that the cache was stopped and started.
Click OK.
To upgrade additional mappings, click the Site-toServer Mapping link and repeat Steps 4 through 8.
Follow these steps to upgrade cache sizes and connection limits.
Open the webcache.xml
file in the Oracle9iAS Release 2 (1.0.2.2.x) Oracle home.
Locate the cache size and connection limit values in the Release 2 (1.0.2.2.x) webcache.xml
file.
In the Web Cache Manager page frame, locate the Properties section in the frame and click the Resource Limits link.
The content area is populated with the current caches.
Select the radio button for the cache you want and click Edit Selected.
The Edit Resource Limits window opens.
Edit or values for the cache and click Submit.
The Web Cache Manager page reappears.
Click Apply Changes.
The page refreshes with a message to restart Web Cache.
Click Restart.
A dialog box opens with a message that the cache was stopped and started.
Click OK.
If applicable, change the Maximum Cached Object Size by following these steps:
In the Web Cache Manager page frame, locate the Properties section in the frame and click the Resource Limits link.
Click Edit.
The Edit Maximum Cached Object Size window opens.
Do one of the following:
Click the Don't set maximum cache size radio button
Click the Set maximum cached object size: radio button and enter a value for the size.
Click Submit.
The Web Cache Manager page reappears.
Click Apply Changes.
The page refreshes with a message to restart Web Cache.
Click Restart.
A dialog box opens with a message that the cache was stopped and started.
Click OK.
Follow these steps to upgrade trusted subnet selections.
Open the webcache.xml
file in the Oracle9iAS Release 2 (1.0.2.2.x) Oracle home.
Locate the trusted subnet definitions in the Release 2 (1.0.2.2.x) webcache.xml
file.
In the Web Cache Manager page frame, locate the Properties section in the frame and click the Security link.
The content area is populated with security settings.
Click Change Trusted Subnets.
The Change Trusted Subnets window opens.
Click the radio button to select the subnets you want (entering IP addresses if applicable) and click Submit.
The Web Cache Manager page reappears.
Click Apply Changes.
The page refreshes with a message to restart Web Cache.
Click Restart.
A dialog box opens with a message that the cache was stopped and started.
Click OK.
Follow these steps to upgrade error page selections.
Open the webcache.xml
file in the Oracle9iAS Release 2 (1.0.2.2.x) Oracle home.
Locate the error page definitions in the Release 2 (1.0.2.2.x) webcache.xml
file.
In the Web Cache Manager page frame, locate the Origin Servers, Sites and Load Balancing section in the frame and click the Error Pages link.
The content area is populated with error page information.
Click the radio button to select the site name or default pages and click Edit Selected.
The Edit Error Pages window opens.
Enter file names for the error pages and click Submit.
The Web Cache Manager page reappears.
Click Apply Changes.
The page refreshes with a message to restart Web Cache.
Click Restart.
A dialog box opens with a message that the cache was stopped and started.
Click OK.
On UNIX systems, OracleAS Web Cache requires root privilege when:
It is configured to run on ports lower than 1024.
It is configured to run as a user other than the user that installed it.
It is configured to support more than 1024 connections (including connections to origin servers and OracleAS Web Cache cluster members.
To grant OracleAS Web Cache root privilege, execute the following command:
<
destination_MT_OH
>/webcache/bin/webcache_setuser.sh
See the Oracle Application Server Web Cache Administrator's Guide in the Oracle Application Server documentation Library for more information on the setuser.sh
script.
Perform the following steps to ensure that OracleAS Web Cache is functioning correctly after the upgrade:
Try to access the normal listening ports.
Send HTTP requests to OracleAS Web Cache and check the responses.
Use the Administration user interface (which uses the Administration port) to display statistics.