The Web Cache normally is positioned
directly in front of the Application Server. Itís job is to server
cached objects (both static and dynamic) to reduce the load on the
Application Server and Customer Database. The Web Cache also load
balances request across the available Application Servers (using defined
weightings to accommodate server with different capabilities).
Although very effect at being the Application Serverís front-end, it
also excels are providing caching at remote locations.
With Oracleís vision of placing all
you data in one secure, fault tolerant location, remote offices could
experience network/Internet delays that become unacceptable to the user.
Placing Web Cache at the remote office allows it to locally serve cached
objects, reducing the network delay.
Remote Web Caches need to connect to the Application
Server directly, not the ASís Web Cache. Never have one Web
Cache requesting through another web cache.
Web Cache can still load balance to multiple
You can not cluster remote Web Caches.
Your object invalidation methodology must invalidate
objects in all Web Caches, including the remote ones.
By adding a small commodity server
running Web Cache at a remote location, you significantly improve you
user experience at a very low cost.
App Server Support?
I'm now offering personal app server mentoring for Oracle DBAs who
must quickly learn the intricate details of Oracle9iAS. You can
have an Oracle expert right at your fingertips, anytime day or night.
We work with dozens of App Server Oracle databases every year, so we
know exactly how to quickly assist you with any Oracle9iAS or Oracle
Application Server 10g question.
Call 800-766-1884 for a custom evaluation.
Burleson Oracle Consulting
Kittrell, NC, USA, 27544