How Oracle Web Cache works?
For overview on web cache read my this post - http://weblogicserveradministration.blogspot.com/2012/12/oracle-web-cache-for-weblogic-server.html
Note:
Oracle Web Cache 11g is packaging with Oracle Web Tier product. It is no longer part of the Application Server product. Oracle Web Cache 11g is based on Oracle WebLogic domain structure and it works with both Oracle Application Server and WebLogic Server.
Below are the steps shows how your browser interact with the Oracle Web Cache
A browser sends a request to a Web site named www.company.com:80, This request in turn generates a request to Domain Name System (DNS) for the IP address of the Web site
NDS returns the IP address of the load balancer for the site that is 144.25.190.240
The browser sends the request for the Web page to the load balancer. In turn, the load balancer sends the request to Oracle Web Cache server 144.25.190.241.
If the requested content is in its cache, then Oracle Web Cache sends the content directly to the browser. This is called a cache hit.
If Oracle Web Cache does not have the requested content or the content is stale or invalid, it hands the request off to application Web server 144. 25.190.242. This is called a cache miss.
The application Web server sends the content to Oracle Web Cache.
Oracle Web Cache sends the content to the client and stores a copy of the page in cache. A page stored in the cache is removed when it becomes invalid or outdated. The invalidation period can be configured using the Web Cache Administration Manager.
Features of Oracle Web Cache 11G
Request filtering:
You can configure Oracle Web Cache with request filters to take actions on incoming requests based on certain attributes of the request. An incoming request must pass through configured request filters for a given site before Oracle Web Cache processes it. By configuring request filters, you can prevent malicious code from exploiting software vulnerabilities.
MIME Type Match Criteria for Caching Rules:
In addition to specifying the criteria for matching a caching rule to incoming requests based on the URL expression, you can base the match evaluation on the value of the content-type response header of objects. This feature simplifies the definition of caching rules, reduces the overall number of caching rules, and improves Oracle Web Cache performance.
Invalidation using response headers:
You can enable an origin server to invalidate cached content through an HTTP response header.
Request-based logging:
Oracle Web Cache stores every request internally and then writes them in bulk after the request to the event logs.
Oracle Diagnostic Logging (ODL) format for event logs:
Oracle Web Cache supports the ODL format, which provides a common format for all diagnostic messages and log files.
Audit logging:
Oracle Web Cache supports the Common Audit Framework for providing a uniform system for administering audits across Oracle Fusion Middleware components. The audit log files generated by Oracle Web Cache processes provide important information that can help to identify and diagnose potential security performance and configuration issues.
Secure caching:
You can configure Oracle Web Cache to support caching content that is secured by Oracle Single Sign-On authentication with no other authorization requirements.
Required Software's
Oracle Weblogic Server
Oracle Application Development Runtime ( This will give you EM console application )
Oracle OHS
Note : -
Oracle Web Cache can be monitored using the Oracle Enterprise Manager console or standalone Web Cache Administration console. A typical WebLogic Server installation does not included the Enterprise Manager. In order to add the Oracle Enterprise Manager feature to your existing WebLogic Server, you can install the Oracle Application Development Runtime product.
Oracle offers two tools for managing Oracle Web Cache:
Oracle Web Cache Manager
Installation and Configuration Procedure
1. Install Weblogic Server
2. Install Application Development Runtime
Select the same Middleware Home you have selected during weblogic installation
If you haven't created domain prior to ADR installation then go to next step, otherwise run your config.sh
again, select option extend the existing domain, select your existing domain, during application selection
select enterprises manager option, once extended, access your em console like http://host:port/em
3. Install Web cache component ( you have to run Oracle OHS installer for this )
During installation on configure components page, select all three options, "oracle HTTP server" ( optional
- if you want to use it ),"Oracle Web cache", "Associated selected components with weblogic domain" ( if
you want to monitor and administration it via EM console ),
Further details I will post soon...if you need it urgently write me on mnbloghelpdesk@gmail.com
No comments:
Post a Comment