5
Initial Setup and Configuration

This chapter describes the steps to initially configure Oracle Web Cache to begin caching application Web server content after installation.

This chapter contains these topics:

• Task 1: Start Oracle Web Cache

• Task 2: Modify Security Settings

• Task 3: Specify Web Site Settings

• Task 4: Set Resource Limits

• Task 5: (Optional) Modify Ports for Administration, Invalidation, and Statistics Monitoring Requests

• Task 6: (Optional) Configure the Oracle Wallet

• Task 7: Specify Caching Rules

• Task 8: Restart Oracle Web Cache

Task 1: Start Oracle Web Cache

To start Oracle Web Cache to begin initial configuration:

1. If not currently logged on to the Oracle Web Cache computer, log in with the user ID of the user that performed the installation.

2. Start Oracle Web Cache. From the command line, enter:

   webcachectl start
   

Task 2: Modify Security Settings

When Oracle Web Cache is installed, it is set up with default passwords for administration and invalidation requests. In addition, the computer on which you installed Oracle Web Cache is the default trusted host.

To change the security settings:

1. Start Oracle Web Cache Manager.

   See Also: "Starting Oracle Web Cache Manager"

2. Change the password for the administrator.

   Configuration and operational tasks can be performed with the Oracle Web Cache administrator user. The administrator user has a default password of administrator set up during installation. Before you begin configuration, change the default password to a secure password.

   1. In the navigator pane, select Administering Oracle Web Cache > Security.

      The Security page appears in the right pane.

   2. In the Security page, choose Change Admin Password under Administration User.

      The Change Administration User Password dialog box appears.

   3. Enter administrator in the Old Password field and a new password between four and 10 characters in the New Password and Confirm New Password fields.

   4. Choose Submit.

3. Optionally, change the password for the invalidation administrator.

   The invalidation administrator has a user ID of invalidator, whose default password of invalidator is set up during installation.

   1. In the Security page, choose Change Invalidation Password under the Invalidation User.

      The Change Invalidation User Password dialog box appears.

   2. Enter invalidator in the Old Password field, and a new password between four and 10 characters in the New Password and Confirm New Password fields.

   3. Choose Submit.

4. Optionally, change the trusted subnet or trusted host from which Oracle Web Cache and invalidation administration can take place.

   By default, the computer on which you installed Oracle Web Cache is the trusted host.

   1. In the Security page, choose Change Trusted Subnets under the Currently trusted subnets.

      The Change Trusted Subnets dialog box appears.

   2. Select one of the following options:

      All subnets

      Select to allow administration requests from all computers in all the subnets in the network.

      This machine only

      Select to allow administration and invalidation requests from only this computer.

      Enter list of IPs

      Select to allow administration and invalidation requests from all IP addresses you enter in a comma-separated list. You can enter IP addresses in one of the following formats:

      • Complete IP address in dot notation, including the network number, subnet address, and unique host number

        Example: 10.1.2.3

      • Network/netmask pair for subnet restriction through masking

        Example: 10.1.0.0/255.255.0.0 allows all the hosts in the 10.1 subnet access.

      • Network/nnn Classless Inter-Domain Routing (CIDR) specification to require nnn bits from high end to match

        Example: 10.1.0.0/16 allows all the hosts in the 10.1 subnet access. This example is similar to the network/netmask example, except the netmask consists of nnn high-order 1 bits.

   3. Choose Submit.

5. Optionally, change the user ID and group ID for the Oracle Web Cache executables on UNIX.

   By default, the user that performed the installation is the owner of Oracle Web Cache executables. Only this can user can execute webcachectl start|stop commands.

   1. In the navigator pane, select Administering Oracle Web Cache > Process Identity.

      The Process Identity page appears in the right pane.

   2. In the Process Identity page, choose Change IDs.

      The Change Process Identity dialog box appears.

   3. Enter the new user in the New User ID field and the group ID of the user in the New Group ID field.

   4. Choose Submit.

6. In the Oracle Web Cache Manager main window, choose Apply Changes.

   Note: If you changed the password for the administrator user in Step 2, you must restart the admin server process with the webcachectl start command when performing "Task 8: Restart Oracle Web Cache".

Task 3: Specify Web Site Settings

For Oracle Web Cache to act as a virtual server for a Web site, configure Oracle Web Cache with information about the Web site, including the host names of the application Web servers. In addition, specify a listening port from which Oracle Web Cache can receive browser requests.

To configure Oracle Web Cache with Web site information:

1. Configure the application Web servers for the Web site.

   By default, the listening port and host name of the Oracle HTTP Server are configured. Oracle HTTP Server has a default listening port of 7777 on UNIX and 80 on Windows.

   1. In the navigator pane, select Administering Web Sites > Application Web Servers.

      The Application Web Servers page appears in the right pane.

   2. In the Application Web Servers page, choose Add.

      The Edit/Create Application Web Server page dialog box appears.

   3. In the Hostname field, enter the host name of the application Web server.

   4. In the Port field, enter the listening port from which the application Web server will receive Oracle Web Cache requests.

   5. In the Capacity field, enter the number of concurrent connections that the application Web server can sustain.

      In multiple application Web server configurations, the capacity of an individual server is weighted against the total capacity of all configured application Web servers. When capacity is set, Oracle Web Cache assigns a weighted load percentage to the application Web server. The load specifies the percentage of requests that this application Web server will handle. The load percentage is calculated from the following formula:

      Application Web Server Capacity / Total Capacity of All Application Web 
      Servers
      
      

      For example, if one application Web server has a capacity of 50 and a second application Web server has a capacity of 40 for a total capacity of 90, then the first server is assigned a load percentage of 55 and the second server is assigned a load percentage of 45.

      50/90 = 55%
      40/90 = 45%
      

      If this is the only application Web server, then the load will be 100 regardless of the capacity.

      The maximum number of concurrent connections that an application Web server can handle is determined by load testing the application Web server until it runs out of CPU, responds slowly, or until a backend database reaches full capacity.

   6. In the Failover Threshold field, enter the number of allowed continuous request failures before Oracle Web Cache considers the application Web server down.

      The default is five requests.

      If an application Web server fails any time after Oracle Web Cache has started to send a request, then Oracle Web Cache increments the failure counter. The failure counter is reset in the event of a successful application Web server response. A request is considered failed if:

      • There are any network errors

      • The HTTP response status code is either less than 100, or is one of the 500 (Internal Server Error), 502 (Bad Gateway), 503 (Service Unavailable), or 504 (Gateway Timeout) messages

      Once the threshold is met, Oracle Web Cache considers the application Web server down and uses other application Web servers for future requests. When an application Web server is down, Oracle Web Cache starts polling the application Web server. It does this by sending requests to the URL specified in the Ping URL field. When Oracle Web Cache is able to successfully get a response from the application Web server without any network errors and the HTTP response code is not less than 100, or equal to 500, 502, 503, 504, it considers that application Web server live again and uses it for future requests.

      Note: The threshold does not apply if Oracle Web Cache cannot connect to an application Web server. In this case, Oracle Web Cache immediately considers the application Web Cache down and does not use it for future requests. The failover to other live application Web servers does not apply if there is only one live application Web server left.

   7. In the Ping URL field, enter the URL that Oracle Web Cache will use to poll an application Web server that has reached its failover threshold.

   8. In the Ping Interval (seconds) field, enter the time in seconds that Oracle Web Cache will poll an application Web server that has reached its failover threshold.

      The default is 10 seconds.

   9. Choose Submit.

2. Configure a listening port from which Oracle Web Cache will receive browser requests.

   By default, Oracle Web Cache listens with the HTTP protocol on port 1100. It may be necessary to add an additional listening port if you want to assign Oracle Web Cache a port that an application Web server was previously listening on. In addition, you can replace the HTTP listening port to an HTTPS listening port to cache pages for HTTPS requests.

   1. In the navigator pane, select Administering Web Sites > Oracle Web Cache Listen Ports.

      The Oracle Web Cache Listen Ports page appears in the right pane.

   2. In the Oracle Web Cache Listen Ports page, choose Add.

      The Edit/Create Oracle Web Cache Listen Ports page dialog box appears.

   3. In the Oracle Web Cache IP Address field, enter the IP address of the computer running Oracle Web Cache.

   4. In the Oracle Web Cache Listen Port field, enter the listening port from which Oracle Web Cache will receive Web browser requests for the Web site.

      Ensure that this port number is not already in use.

   5. From the Protocol list, select either HTTP to accept HTTP browser requests on the port or HTTPS to accept HTTPS browser requests on the port.

      Note: In this release, Oracle Web Cache has no capability for permitting only HTTPS on an HTTPS protocol. In other words, both HTTP and HTTPS requests will be accepted. If you want only HTTPS requests to be accepted, Oracle Corporation recommends removing HTTP listening ports.

      See Also: "Secure Sockets Layer (SSL) Support"

   6. Choose Submit.

3. In the Oracle Web Cache Manager main window, choose Apply Changes.

Task 4: Set Resource Limits

To set resource limits for Oracle Web Cache, configure the following attributes:

• Cache Memory

• Connection Limit

Cache Memory

When the maximum cache memory limit is reached, Oracle Web Cache performs garbage collection. During garbage collection, Oracle Web Cache removes the less popular and less valid documents from the cache in favor of the more popular and more valid documents.

To avoid swapping documents in and out of the cache, it is crucial to configure enough memory for the cache. Generally, the amount of memory (maximum cache size) for Oracle Web Cache should be set to at least 256 MB. By default, the maximum cache size is set to 500 MB, which is sufficient for most caches.

To be more precise in determining the maximum amount of memory required, you can take the following steps:

1. Determine what documents you want to cache and the size and type of each document.

   One way to do this is to look at existing web server logs for one day to see what documents are popular. From the list of URLs in the log, decide which ones you want to cache. Retrieve the documents and get the size of each document.

2. Calculate the amount of memory needed. The way you calculate it may differ depending on the version of Oracle Web Cache.

   The amount of memory that Oracle Web Cache uses to store a document depends on whether the document is larger or smaller than 4 KB:

   • If a document is smaller than 4 kilobytes (KB), Oracle Web Cache uses a buffer of 4 KB to store the HTTP body.

   • If a document is 4 KB or larger, Oracle Web Cache uses buffers of 32 KB to store the HTTP body. For example, if a document is 40 KB, Oracle Web Cache uses two 32 KB buffers to store the HTTP body.

   • Regardless of the size of the body, Oracle Web Cache uses 8 KB to store the HTTP response header.

   Use the following formula to determine an estimate of the maximum memory needed:

   ( X * ( 4KB + 8KB ) ) + ( Y * (( [m/32] * 32KB ) + 8KB )) + 100MB
   
   

   In the formula:

   • X is the number of documents smaller than 4 KB.

   • 4KB is size of the buffer for the HTTP body for documents smaller than 4 KB.

   • 8KB is the size of the buffer for the HTTP response header.

   • Y is number of documents that are 4 KB or larger.

   • [m/32] is the ceiling of m (the average size, in kilobytes, of documents 4 KB or larger) divided by 32. A ceiling is the closest integer that is greater than or equal to the number.

   • 32KB is size of the buffer for the HTTP body for documents that are 4 KB or larger.

   • 8KB is the size of the buffer for the HTTP response header.

   • 100MB is the base amount, in megabytes, of memory needed to run Oracle Web Cache. This amount includes memory for internal functions such as lookup keys and timestamps.

   For example, assume that you want to cache 5000 documents that are smaller than 4 KB and 2000 documents that are 4 KB or larger and that the larger documents have an average size of 54 KB. Use the formula to compute the maximum memory:

   (5000 * (4KB + 8KB) ) + ( 2000 * (( [54/32] * 32KB ) + 8KB )) + 100MB
   
   

   Using the formula, you need:

   • 60,000 KB for the smaller documents.

   • 144,000 KB for the larger documents. For the HTTP body, you need 64 KB (two 32 KB buffers) for each document, given the average size of 54 KB. For the HTTP response header, you need 8 KB for each document.

   • 100 MB for the base amount of memory needed for Oracle Web Cache.

   This results in an estimate of 300 MB of memory needed.

   Note that this formula does not take into account the complexities of calculating the size of Edge Side Includes (ESI) pages. The only valid method to calculate the size of pages cached with ESI is to monitor the cache.

3. Configure Oracle Web Cache, specifying the result of the formula as the maximum cache size. Remember that the result is only an estimate.

   To specify the maximum cache size:

   1. In the navigator pane, select Administering Oracle Web Cache > Resource Limits.

      The Resource Limits page appears in the right pane.

   2. In the Resource Limits page, choose Change cache size limit.

      The Change Maximum Cache Size dialog box appears.

   3. In the New maximum cache size, enter the result of the formula.

   4. Choose Submit.

   5. In the Oracle Web Cache Manager main window, choose Apply Changes.

   Even though you have specified that certain documents should be cached, not all of the documents are cached at the same time. Only those documents that have been requested and are valid are stored in the cache. As a result, only a certain percentage of your documents are stored in the cache at any given time. That means that you may not need the maximum memory derived by the preceding formula.

4. Start Oracle Web Cache and, using a simulated load or an actual load, monitor the cache to see how much memory it really uses in practice.

   Remember that the cache is empty when Oracle Web Cache starts. For monitoring to be valid, make sure that the cache is fully populated. That is, make sure that the cache has received enough requests so that a representative number of documents are cached.

   The Oracle Web Cache Statistics and the Oracle Web Cache Detailed Statistics Monitor pages provide information about the current memory use and the maximum memory use.

   1. To access the Oracle Web Cache Statistics page, from the navigator pane, select Administering Web Sites > Monitoring Oracle Web Cache > Statistics.

      The Cache Size (in bytes) metric shows the current logical size of the cache. The logical size of the cache is the size of the valid documents in the cache. For example, if the cache contains two documents, one 3 KB and one 50 KB, the cache size is 53 KB, the total of the two sizes. This metric does not show the physical size of the cache.

   2. To access the Oracle Web Cache Detailed Statistics Monitor page, enter the following URL:

      http://web_cache_hostname:statistics_port
      
      

      By default, the statistics port is set to port 4002.

      The Oracle Web Cache Detailed Statistics Monitor page displays the physical size of the cache. The physical size of the cache is the amount of memory used by Oracle Web Cache.

      In the Oracle Web Cache Memory Manager Block Usage table, observe the Current Action Limit and the Current Allocated Memory metrics. The Current Allocated Memory metric is usually smaller than the Current Action Limit metric. If the Current Allocated Memory is close to or greater than the Current Action Limit, increase the maximum cache size.

Connection Limit

In addition to the cache size, it is also important to specify the maximum connection limit to the Oracle Web Cache server. When you configure this limit, set a reasonable number. If you set a number that is too high, then performance can be affected. To help determine the correct number, use various tools available with the operating system. For example, the netstat -a command on UNIX and Windows enables you to determine the number of established connections.

Note that you should set the maximum number of incoming connections in Oracle Web Cache Manager to correctly reflect the maximum number of clients you intend to serve concurrently at any given time. Do not set the value to an arbitrary high value, because Oracle Web Cache sets aside some resources for each connection, adversely affecting performance.

To set the maximum number incoming connections limit:

1. In the navigator pane, select Administering Oracle Web Cache > Resource Limits.

   The Resource Limits page appears in the right pane.

2. In the Resource Limits page, choose Change connections limit.

   The Change Maximum Incoming Connections Limit dialog box appears.

3. In the New maximum connections limit field, enter the new limit.

4. Choose Submit.

5. In the Oracle Web Cache Manager main window, choose Apply Changes.

Connections on UNIX

On most UNIX operating systems, each client connection requires a separate file descriptor. The number of file descriptors that a process can open is usually set to 1024. You can change this number to a higher one, but you must change the ownership of the executable webcached to root and make it executable to all users. In addition, you must add set-user ID permission to the executable. If the ownership of webcached is not changed, Oracle Web Cache fails to start and writes the events to the event_log file.

Oracle Web Cache uses the following formula to calculate the maximum number of file descriptors to be used:

Max_File_Desc = Current_Max_Conn + App_Web_Server_Capacity_Sum + 20  

In the formula:

• Max_File_Desc is the maximum number of file descriptors to be used.

• Current_Max_Conn is the current maximum incoming connections limit for Oracle Web Cache. Set the maximum number of incoming connections using the Administering Oracle Web Cache > Resource Limits page of Oracle Web Cache Manager.

• App_Web_Server_Capacity_Sum is the sum of the capacity for all configured application Web Servers. Set the capacity using the Administering Web Sites > Application Web Servers page of Oracle Web Cache Manager.

• 20 is the number of connections reserved for internal use by Oracle Web Cache.

The Oracle Web Cache server tries to reserve the maximum number of file descriptors (Max_File_Desc) when it starts. If it fails to do so, it does not default to a lower value but logs an error message and fails to start. If the Oracle Web Cache server fails to start because the number of file descriptors required is more that 1024, you must change the ownership of the executable webcached to root and make it executable to all users. In addition, you must add set-user ID permission to the executable.

If the ownership of webcached is not changed, then Oracle Web Cache fails to starts and writes the following events to the event_log file:

20/May/2001:18:18:24 -0800 -- Error: Could not increase number of file/socket 
descriptors to 10220.
20/May/2001:18:18:24 -0800 -- Error: Failed to start the server.

See Also: "Greater Than One Thousand Maximum Connections" for information on changing the ownership of webcached to root Operating system-specific documentation for connection limitations Operating system-specific Oracle HTTP Server powered by Apache Performance Guide for TCP/IP performance tuning tips

Connections on Windows

On Windows NT and 2000, the number of file handles as well as socket handles is limited only by available kernel resources, more precisely, by the size of paged and non-paged pools. However, the number of active TCP/IP connections is restricted by the number of TCP ports the system can open.

The default maximum number of TCP ports is set to 5000 by the operating system. Of those, 1024 are reserved by the kernel. You can modify the maximum number of ports by editing the Windows registry. Windows NT and Windows 2000 allow up to 65536 ports.To change the default, you must add a new value to the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

Add a new value, specifying the following:

• Value Name: MaxUserPort

• Data Type: REG_DWORD

• Data: An integer less than 65536 - 1024

Do not set the maximum number of incoming connections in Oracle Web Cache Manager to a number greater than the number of TCP ports minus 1024. On Windows, Oracle Web Cache does not attempt to reserve file handles or to check that the number of current maximum incoming connections is less than the number of TCP ports.

See Also: Operating system-specific documentation for connection limitations Operating system-specific Oracle HTTP Server powered by Apache Performance Guide for TCP/IP performance tuning tips

Task 5: (Optional) Modify Ports for Administration, Invalidation, and Statistics Monitoring Requests

In addition to receiving HTTP and HTTPS browser request, Oracle Web Cache also receives administration, invalidation, and statistics monitoring requests on specific HTTP or HTTPS listening ports:

http://web_cache_hostname:http_port 
https://web_cache_hostname:https_port 

By default, Oracle Web Cache uses the HTTP protocol to receive these requests. Default port numbers are as follows:

• 4000 for administration and configuration requests from Oracle Web Cache Manager

• 4001 for invalidation requests

• 4002 for statistics monitoring requests

Changing the Default Administration Listening Endpoint

To change the default port number or protocol for administration requests or configuration changes:

1. In the navigator pane, select Administering Oracle Web Cache > Oracle Web Cache Administration Port.

   The Oracle Web Cache Administration Port page appears in the right pane.

2. In the Oracle Web Cache Administration Port page, choose Edit.

   The Change Administration Port dialog box appears.

3. In the New Administration Port field, enter the new port.

4. From the Protocol list, select either HTTP or HTTPS to accept administration requests from one of the following URLs:

   http://web_cache_hostname:administration_port 
   https://web_cache_hostname:administration_port 
   

5. Choose Submit.

6. In the Oracle Web Cache Manager main window, choose Apply Changes.

   Note: When changing the administration port, note the following: Requests to the administration port must originate from a trusted host or a host on a trusted subnet. Trusted hosts and subnets are defined in the Security page (Administering Oracle Web Cache > Security). See "Task 2: Modify Security Settings" for further information. Restart the admin server process with the webcachectl start command when performing "Task 8: Restart Oracle Web Cache".

Changing the Default Invalidation and Statistics Monitoring Listening Endpoints

To change the default port number or protocol for invalidation or statistics monitoring requests:

1. In the navigator pane, select Administering Oracle Web Cache > Oracle Web Cache Administration Port.

   The Oracle Web Cache Invalidation/Statistics Port page appears in the right pane.

2. In the Oracle Web Cache Invalidation/Statistics Port page, choose Edit.

   The Change Invalidation/Statistics Port dialog box appears.

3. In the New Invalidation Port field, enter the new port.

4. From the Protocol list, select either HTTP or HTTPS to accept invalidation requests from one of the following URLs:

   http://web_cache_hostname:invalidation_port 
   https://web_cache_hostname:invalidation_port 
   

5. From the Protocol list, select either HTTP or HTTPS to accept statistics monitoring requests from one of the following URLs:

   http://web_cache_hostname:statistics_port 
   https://web_cache_hostname:statistics_port 
   

   Note: If you enable HTTPS for invalidation or statistics monitoring requests, you cannot use the Oracle Web Cache Manager interface to send the requests. You must submit requests through the URL.

6. Choose Submit.

7. In the Oracle Web Cache Manager main window, choose Apply Changes.

Task 6: (Optional) Configure the Oracle Wallet

If you configured Oracle Web Cache to receive HTTPS browser requests in Step 2 of "Task 3: Specify Web Site Settings", then create a wallet for server-side certification on the computer running Oracle Web Cache. The wallet manages authentication data such as keys, certificates, and trusted certificates needed by the Secure Sockets Layer (SSL). Once the wallet is created, use Oracle Web Cache Manager to specify the location of the wallet.

This section covers the following topics relating to wallet configuration:

• Creating a Wallet

• Specifying the Location of Wallets

• Enabling Wallets to Open on Windows

Creating a Wallet

To create the wallet, use Oracle Wallet Manager.

To start Oracle Wallet Manager:

• On UNIX, run owm from $ORACLE_HOME/bin

• On Windows, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Wallet Manager

  See Also: "Secure Sockets Layer (SSL) Support" Oracle9i Application Server Oracle Wallet Manager User's Guide

Specifying the Location of Wallets

Once the wallet is created, use Oracle Web Cache Manager to specify the location of the wallet. You specify the wallet for the Oracle Web Cache computer when you configure listening ports. Listening ports for a site can share the same wallet.

Wallets have the following default locations:

• /etc/ORACLE/WALLETS/user_name on UNIX

• %USERPROFILE%\ORACLE\WALLETS on Windows NT and Windows 2000

To change the default location of the wallet:

1. In the navigator pane, select Administering Web Sites > Oracle Wallet.

   The Oracle Wallet page appears in the right pane.

2. In the Oracle Wallet page, choose Edit.

   The Change Oracle Wallet dialog box appears.

3. In the Wallet Resource Locator field, enter the location of the wallet.

   On UNIX, use file: to prefix the directory path. On Windows, use file:drive_letter: to prefix the directory path.

4. Choose Submit.

5. In the Oracle Web Cache Manager main window, choose Apply Changes.

Enabling Wallets to Open on Windows

Oracle Web Cache attempts to open wallets at startup on Windows NT and 2000. On Windows NT and 2000, wallets are protected so that only the user that created them can open and use them. By default, Oracle Web Cache services are associated with the local system account, which does not have permission to open wallets.

To enable Oracle Web Cache to open wallets at startup:

1. Create a wallet with an administrator account.

2. Change the system account information for the Oracle Web Cache services:

   Windows NT

   Windows 2000

   Choose the Services icon from the Control Panel window. The Services window appears. Select the OracleHOME_NAMEWebCache service. The Service dialog appears. Choose This Account. By default the LocalSystem user account is associated with the service. Choose "..." next to This Account. The Add User dialog box appears. Select the user that created the wallet from the Names list, and then choose Add. Choose OK to close the Add User dialog box. In the Service dialog box, provide the password for the wallet administrator in the Password field, and then confirm the password in the Confirm Password field. In the Services dialog box, choose OK. Repeat Steps 3 - 9 for the OracleHOME_NAMEWebCacheAdmin and OracleHOME_NAMEWebCacheMon services. In the Services window, choose Close.

   Choose Administrative Tools > Services from the Control Panel window. The Services window appears. Select the OracleHOME_NAMEWebCache service. The OracleHOME_NAMEWebCache Properties dialog appears. Choose the Log On tab. In the Log On tab, choose This account. By default the LocalSystem user account is associated with the service. Choose Browse next to This Account. The Select User dialog box appears. Select the user that created the wallet from the list, and then choose OK. Choose OK to close the Add User dialog box. In the OracleHOME_NAMEWebCache Properties dialog box, provide the password for the wallet administrator in the Password field, and then confirm the password in the Confirm Password field. In the Services dialog box, choose OK. Repeat Steps 3 - 9 for the OracleHOME_NAMEWebCacheAdmin and OracleHOME_NAMEWebCacheMon services.

3. On Windows NT, grant the wallet administrator the right to run Oracle Web Cache as a service.
   1. Choose Start > Programs > Administrative Tools > User Manager.

      The User Manager window appears:

   2. Select the wallet administration, and then choose Policies > User Rights.

      The User Rights Policy dialog box appears:

   3. Choose the Show Advanced User Rights check box, and then select Log on as a service from the Right list.

   4. Select Users from the Grant To list.

      If Users does not exist, create it:

      Choose Add. The Add Users and Groups dialog box appears: Select the name of the local host computer from the List Names From list. Select Users from the Names list, and then choose Add. Choose OK. Users appears in the Grant To list.

   5. Choose OK in the User Rights Policy dialog box.

      The User Manager window reappears.

   6. Choose User > Exit.

      See Also: "Wallet Cannot Be Opened"

Task 7: Specify Caching Rules

Specify the URLs containing the documents you want Oracle Web Cache to cache.

See Also: "Configuring Cacheability Rules"

Task 8: Restart Oracle Web Cache

When Oracle Web Cache is configured, stop it and start it again to read in the new configuration settings. When you stop Oracle Web Cache, all objects are cleared from the cache. In addition, all statistics are cleared. You can stop and start Oracle Web Cache using either Oracle Web Cache Manager or the webcachectl utility on the computer on which Oracle Web Cache software is installed and configured:

Use Oracle Web Cache Manager...	Use the webcachectl Utility...
Start Oracle Web Cache Manager. See Also: "Starting Oracle Web Cache Manager" In the navigator pane, select Administering Oracle Web Cache > Web Cache Operations. The Oracle Web Cache Operations page appears in the right pane. In the Oracle Web Cache Operations page, choose Stop and then Start.	From the command line, enter: webcachectl stop webcachectl start

Note: If you change the administration password in the Security page (Administering Oracle Web Cache > Security) or the administration listening port in the Administration port page (Administering Oracle Web Cache > Administration Port), you must restart the admin server process with the webcachectl start command.

See Also: "Starting and Stopping Oracle Web Cache"