About Search Keys in Invalidations

Invalidating Content 7-21 For more information, see: ■ http:www.rfc-editor.org for information about password Base64 encoding ■ readme.examples.htmlfor further information about using the EncodeBase64.java script to generate the Base64 string for invalidator:invalidator_password. This file is located in the following directories: UNIX ORACLE_HOMEwebcachedocs Windows ORACLE_HOME\webcachedocs ■ Section 5.2 for further information about changing the invalidation password 3. Enter one carriage return. 4. Send the invalidation request with XML syntax, as specified in Section 7.5 .

7.7.2 Using Oracle Web Cache Manager to Send Invalidation Requests

Oracle Web Cache Manager provides an easy-to-use interface for invalidating cached objects. The advantage of using this interface is that the administrator is isolated from the intricacies of the HTTP and XML formats, and consequently, there is less chance for error. The administrator need only specify which objects to invalidate and how how quickly those objects should be invalidated. Oracle Web Cache Manager enables you to send either basic invalidation request for invalidation one object, or an advanced invalidation request for multiple objects, as described in the following topics: ■ Section 7.7.2.1, Submitting Basic Invalidation Requests ■ Section 7.7.2.2, Submitting Advanced Invalidation Requests

7.7.2.1 Submitting Basic Invalidation Requests

To send a basic invalidation request using Oracle Web Cache Manager:

1. From Oracle Web Cache Manager, in the navigator frame, select Operations

Basic Content Invalidation. See Section 2.7.2 . The Basic Content Invalidation page appears in the right pane.

2. From the For Cache list, select a cache. The list displays multiple caches only if

you configured a cache cluster. If you configured the cluster to propagate Note: If you receive the following error when you submit invalidation requests from the Basic Content Invalidation or Advanced Content Invalidation pages, restart the cache or admin server processes. Internal error: cant connect to Oracle Web Cache Invalidation Listening Port If you change the property of an invalidation port, restart the cache server process. If you change the password for the administrator account in the Security page, restart the cache and admin server processes. Until you restart the cache server process for either configuration change, invalidation requests return the error. See Section 2.13 for restart instructions. 7-22 Oracle Fusion Middleware Administrators Guide for Oracle Web Cache invalidation, the cache you select is designated the invalidation coordinator, which propagates the invalidation request to other cache cluster members. If you did not configure the cluster to propagate invalidation, the cache you select is the only cache from which objects are invalidated.

3. In the Search Criteria section, select the search criteria:

■ Remove all cached objects: Select to remove all objects from the cache. ■ Enter exact URL for removal : Specify the URL of the objects to be invalidated. Include the complete path and file name. Note: Because Oracle Web Cache escapes the following characters, you can enter them in this field: ampersand , greater than sign , less than sign , double quotes , and single quotes . 4. Optionally, you can preview the list of objects to be invalidated to ensure that you are removing only the objects you want to remove. To preview the list of objects:

a. In the Action section, choose Preview list of objects that match invalidation

criteria .

b. Specify the Object Range:

– From: Enter the number representing the first object to be listed. Oracle Web Cache begins the count of objects with the number 0. – To: Enter the number of objects to be listed. If fewer objects than the number specified meet the invalidation criteria, Oracle Web Cache lists the URLs for only those objects that meet the crite- ria. If more objects than the number specified meet the invalidation criteria, Oracle Web Cache lists the URLs for the number of objects requested. It also returns the total number of objects that meet the invalidation criteria. To obtain the list of URLs for additional objects, send another preview request with a different From number that specifies the start of the next set of objects.

c. Click Submit.

Oracle Web Cache displays the Invalidation Preview Results message box, which lists the objects that meet the invalidation criteria. Oracle Web Cache Manager lists only those objects that are valid. Although the cache may contain objects that are expired or that have been invalidated, those objects are not listed. If the listed objects are for those to invalidate, continue with the next step. If they are not, modify the invalidation criteria and preview the list again.

5. In the Action section, select an option to specify how to process invalid objects:

■ Remove immediately: Oracle Web Cache marks objects as invalid and removes them immediately. A object is refreshed from the origin server when the cache receives the next request for it. ■ Remove objects no later than number time after submission: Oracle Web Cache marks objects as invalid and then refreshes them based on origin server capacity. Enter the maximum time in which the objects can reside in the cache. When you select this option, Oracle Web Cache applies heuristics to determine when is best time to no longer serve the document.

6. Click Submit.