Performance Tuning for Oracle WebCenter Content 11g - Fishbowl ...

IDOC script includes can be cached, so the html will be dynamically rendered and then placed in session scope for a
specific user or application scope for all users. The cacheInclude method takes the include name, scope, and life
span as required parameters. For example, the std_page_begin include would be cached for ten minutes for each
user.
11g continues to lack a default success status code or message returned with all services. Content Services
typically indicate an error by setting StatusCode property to a non-zero number. CIS, RIDC, and several other
integration methods will potentially throw an exception when there are problems, but will absolutely throw an
exception if you look for the StatusCode property and it is missing. One can either trust the service will throw an
exception and assume it works, or modify the content server to set a default success status code.
Reverse Proxy
When architecting a website for high performance using Webcenter Content, a reverse proxy can be used to
improve both performance and security for your site. A reverse proxy functions as a gateway to your network and
adds an additional layer of caching for site visitors that will help to improve page response time, particularly under
heavy load.
Typically, a reverse proxy will reside in the DMZ of your network and will be the entry point for users accessing your
site. The standard process flow for a user accessing a site behind a reverse proxy is as follows:
1. A user enters http://www.mysite.com in a browser.
2. DNS directs the user to the reverse proxy server that is sitting in your DMZ.
3. The reverse proxy determines if the request is being made for static content or dynamic content.
4. If static content is being requested, the reverse proxy will check its cache and will return the cached page to
the user if the page is found in the cache.
5. If dynamic content is being requested or if the reverse proxy does not have the page in its cache, it will send
a request through the firewall to a web server inside your network to retrieve the requested page and will
return that page to the user.
The performance gains from caching at the reverse proxy level are obviously contingent on a number of factors
including the number of static resources and pages that users are requesting, the frequency at which those items
are accessed, and the hardware-network infrastructure that is being used. One popular reverse caching application,
Varnish Cache, claims to improve delivery by a factor of 300 – 1000x depending on architecture when serving a
page from cache (www.varnish-cache.org),.
Besides the caching advantage of this model, your site also gains an additional level of security by implementing a
reverse proxy. All requests that are made to your site are being filtered through the remote proxy server, which
limits an end-user from distinguishing server names or other network architecture information that could
potentially be used to compromise your systems. Additionally, there is only a single entry point through your
firewall, namely between your proxy server and your web server, so network administrators have considerably more
control over limiting the traffic that is allowed past the firewall.
© 2012. Fishbowl Solutions, Inc.