Summary

In this chapter we covered the WC server. You saw how it's able to receive incoming requests before they reach the OHS origin server and send back cached content to the client. This improves performance for the client while reducing the load on the back-end origin servers, network, and databases. This allows for a more scalable solution with a less expensive WC server than one that manages larger, multinode application-server clusters.

You saw how WC is configured and looked at the administrative management tools. The setup and configuration of WC is relatively simple and you were able to create a new WC site ( wc-test. name ) in a matter of minutes. The WC Manager tool provides multiple monitoring, logging, and diagnostics pages for you to troubleshoot errors and monitor performance.

By default, WC already caches content that generally should be cached: HTML files, PDF files, and other image files. Using the WC Manager pages, you saw how caching rules can be created or edited to allow more content to be cached. Expiration time frames and compression of documents were also covered. Finally, we showed you how content can be manually invalidated by the administrator and how custom invalidation code can be written using preexisting templates.