Sample app: Web Cache and ESI

Download a new sample application and learn how to deliver dynamic, personalized content faster with Oracle9iAS Web Cache and Edge Side Includes (ESI). Oracle9iAS Web Cache and ESI can also accelerate the performance of e-business applications and boost productivity of employee-facing applications across an intranet.
Regards,
-rh

The source code and docs have been updated.

Similar Messages

IE browser and Web Cache and SSL - Internet Explorer cannot display the web page

When using IE8, IE9, or IE10 with Web Cache and SSL certain pages which display a lot of data returns the error - "Internet Explorer cannot display the web page."
if we eliminate SSL but continue to use Web Cache, the error does *not* reproduce & If we eliminate Web Cache altogether the error again does *not* reproduce. The error is only reproducible when we use SSL with Web Cache and if we use IE and we access *large* pages. The error is not reproducible with Firefox or Chrome. This is a Web Tier 11.1.1.7 installation with WebLogic 10.3.6 & Red Hat Enterprise 5 Linux x86-64
Event_log shows below errors.
[2013-06-13T16:34:35-04:00] [webcache] [NOTIFICATION:1] [WXE-09002] [logging] [ecid: ] Generated by Oracle Web Cache on Thu Jun 13 16:34:35 2013 - Build 11.1.1.7.0 130113.0721
[2013-06-13T16:34:36-04:00] [webcache] [NOTIFICATION:1] [WXE-08513] [logging] [ecid: ] Cache server process ID 4469 is starting up.
[2013-06-13T16:34:36-04:00] [webcache] [NOTIFICATION:1] [WXE-09612] [main] [ecid: ] Oracle Web Cache 11g (11.1.1.6), Build 11.1.1.7.0 130113.0721
[2013-06-13T16:34:37-04:00] [webcache] [NOTIFICATION:1] [WXE-13002] [config] [ecid: ] Maximum allowed incoming connections are 1000
[2013-06-13T16:35:00-04:00] [webcache] [NOTIFICATION:1] [WXE-09441] [stats] [ecid: ] DMS enabled
[2013-06-13T16:35:28-04:00] [webcache] [NOTIFICATION:1] [WXE-12209] [cluster] [ecid: ] A 1 node cluster successfully initialized
[2013-06-13T16:35:29-04:00] [webcache] [NOTIFICATION:1] [WXE-09614] [main] [ecid: ] The following Oracle Web Cache internal files are pre-populated to the cache: [[
        /nssb-p.adm.fit.edu:7785/_oracle_http_server_webcache_static_.html
        /nssb-p.adm.fit.edu:4448/_oracle_http_server_webcache_static_.html
[2013-06-13T16:35:29-04:00] [webcache] [NOTIFICATION:1] [WXE-09614] [main] [ecid: ] [[
The following Oracle Web Cache internal files are pre-populated to the cache: [[
        /nssb-p.adm.fit.edu:7785/_oracle_http_server_webcache_checkserviceavailability_.html
        /nssb-p.adm.fit.edu:4448/_oracle_http_server_webcache_checkserviceavailability_.html
[2013-06-13T16:35:29-04:00] [webcache] [NOTIFICATION:1] [WXE-09608] [main] [ecid: ] The cache server process started successfully.
[2013-06-13T16:35:29-04:00] [webcache] [WARNING:1] [WXE-12104] [utl] [ecid: ] Oracle Web Cache process has page faulted
[2013-06-13T16:44:22-04:00] [webcache] [ERROR:32] [WXE-11904] [security] [ecid: ] SSL handshake fails SSL-29049
[2013-06-13T16:44:22-04:00] [webcache] [WARNING:1] [WXE-11905] [security] [ecid: ] SSL additional information: The record type is unknown.
[2013-06-13T16:44:22-04:00] [webcache] [WARNING:1] [WXE-11905] [security] [ecid: ] SSL additional information: Remote IP [163.118.22.16]:55145
[2013-06-13T16:44:22-04:00] [webcache] [WARNING:1] [WXE-11905] [security] [ecid: ] SSL additional information: Local IP 163.118.170.70:4448
[2013-06-13T16:44:22-04:00] [webcache] [WARNING:1] [WXE-11906] [security] [ecid: ] SSL details: SSL error during handshake (details: internal=The record type is unknown. system=Success)
[2013-06-13T16:44:27-04:00] [webcache] [ERROR:32] [WXE-11904] [security] [ecid: ] SSL handshake fails SSL-29049
[2013-06-13T16:44:27-04:00] [webcache] [WARNING:1] [WXE-11905] [security] [ecid: ] SSL additional information: The record type is unknown.
[2013-06-13T16:44:27-04:00] [webcache] [WARNING:1] [WXE-11905] [security] [ecid: ] SSL additional information: Remote IP [163.118.22.16]:55144
[2013-06-13T16:44:27-04:00] [webcache] [WARNING:1] [WXE-11905] [security] [ecid: ] SSL additional information: Local IP 163.118.170.70:4448
[2013-06-13T16:44:27-04:00] [webcache] [WARNING:1] [WXE-11906] [security] [ecid: ] SSL details: SSL error during handshake (details: internal=The record type is unknown. system=Success)
[2013-06-13T16:44:27-04:00] [webcache] [ERROR:32] [WXE-11904] [security] [ecid: ] SSL handshake fails SSL-29049
[2013-06-13T16:44:27-04:00] [webcache] [WARNING:1] [WXE-11905] [security] [ecid: ] SSL additional information: The record type is unknown.
[2013-06-13T16:44:27-04:00] [webcache] [WARNING:1] [WXE-11905] [security] [ecid: ] SSL additional information: Remote IP [163.118.22.16]:55148
[2013-06-13T16:44:27-04:00] [webcache] [WARNING:1] [WXE-11905] [security] [ecid: ] SSL additional information: Local IP 163.118.170.70:4448
[2013-06-13T16:44:27-04:00] [webcache] [WARNING:1] [WXE-11906] [security] [ecid: ] SSL details: SSL error during handshake (details: internal=The record type is unknown. system=Success)
[2013-06-13T16:44:35-04:00] [webcache] [ERROR:32] [WXE-11904] [security] [ecid: ] SSL handshake fails SSL-28864
[2013-06-13T16:44:35-04:00] [webcache] [ERROR:32] [WXE-11904] [security] [ecid: ] SSL handshake fails SSL-28864
[2013-06-13T16:44:47-04:00] [webcache] [WARNING:1] [WXE-11905] [security] [ecid: ] SSL additional information: This error occurred because the peer closed the connection.
[2013-06-13T16:44:47-04:00] [webcache] [WARNING:1] [WXE-11906] [security] [ecid: ] SSL details: success during initialization (details: internal=success system=Success)
[2013-06-13T16:44:47-04:00] [webcache] [WARNING:1] [WXE-11905] [security] [ecid: ] SSL additional information: This error occurred because the peer closed the connection.
[2013-06-13T16:44:47-04:00] [webcache] [WARNING:1] [WXE-11906] [security] [ecid: ] SSL details: success during initialization (details: internal=success system=Success)
[2013-06-13T16:44:47-04:00] [webcache] [WARNING:1] [WXE-11905] [security] [ecid: ] SSL additional information: This error occurred because the peer closed the connection.
[2013-06-13T16:44:47-04:00] [webcache] [WARNING:1] [WXE-11906] [security] [ecid: ] SSL details: success during initialization (details: internal=success system=Success)
[2013-06-13T16:44:47-04:00] [webcache] [WARNING:1] [WXE-11905] [security] [ecid: ] SSL additional information: This error occurred because the peer closed the connection.
[2013-06-13T16:44:47-04:00] [webcache] [WARNING:1] [WXE-11906] [security] [ecid: ] SSL details: success during initialization (details: internal=success system=Success)
[2013-06-13T16:44:47-04:00] [webcache] [WARNING:1] [WXE-11905] [security] [ecid: ] SSL additional information: This error occurred because the peer closed the connection.
[2013-06-13T16:44:47-04:00] [webcache] [WARNING:1] [WXE-11906] [security] [ecid: ] SSL details: success during initialization (details: internal=success system=Success)
[2013-06-13T16:44:47-04:00] [webcache] [WARNING:1] [WXE-11905] [security] [ecid: ] SSL additional information: This error occurred because the peer closed the connection.
[2013-06-13T16:44:47-04:00] [webcache] [WARNING:1] [WXE-11906] [security] [ecid: ] SSL details: success during initialization (details: internal=success system=Success)
[2013-06-13T16:45:18-04:00] [webcache] [WARNING:1] [WXE-11905] [security] [ecid: ] SSL additional information: This error occurred because the peer closed the connection.
[2013-06-13T16:45:18-04:00] [webcache] [WARNING:1] [WXE-11906] [security] [ecid: ] SSL details: success during initialization (details: internal=success system=Success)
[2013-06-13T16:45:22-04:00] [webcache] [ERROR:32] [WXE-11904] [security] [ecid: ] SSL handshake fails SSL-28864
[2013-06-13T16:45:22-04:00] [webcache] [ERROR:32] [WXE-11904] [security] [ecid: ] SSL handshake fails SSL-28864
[2013-06-13T16:45:38-04:00] [webcache] [WARNING:1] [WXE-11905] [security] [ecid: ] SSL additional information: This error occurred because the peer closed the connection.
[2013-06-13T16:45:38-04:00] [webcache] [WARNING:1] [WXE-11906] [security] [ecid: ] SSL details: success during initialization (details: internal=success system=Success)
[2013-06-13T16:45:38-04:00] [webcache] [WARNING:1] [WXE-11905] [security] [ecid: ] SSL additional information: This error occurred because the peer closed the connection.
[2013-06-13T16:45:38-04:00] [webcache] [WARNING:1] [WXE-11906] [security] [ecid: ] SSL details: success during initialization (details: internal=success system=Success)
[2013-06-13T16:45:38-04:00] [webcache] [WARNING:1] [WXE-11905] [security] [ecid: ] SSL additional information: This error occurred because the peer closed the connection.
[2013-06-13T16:45:38-04:00] [webcache] [WARNING:1] [WXE-11906] [security] [ecid: ] SSL details: success during initialization (details: internal=success system=Success)
[2013-06-13T16:45:38-04:00] [webcache] [WARNING:1] [WXE-11905] [security] [ecid: ] SSL additional information: This error occurred because the peer closed the connection.
[2013-06-13T16:45:38-04:00] [webcache] [WARNING:1] [WXE-11906] [security] [ecid: ] SSL details: success during initialization (details: internal=success system=Success)
[2013-06-13T16:45:41-04:00] [webcache] [WARNING:1] [WXE-11905] [security] [ecid: ] SSL additional information: This error occurred because the peer closed the connection.
[2013-06-13T16:45:41-04:00] [webcache] [WARNING:1] [WXE-11906] [security] [ecid: ] SSL details: success during initialization (details: internal=success system=Success)
Any help or suggestions are greatly appreciated
Tnx a lot,
Lokesh

Hello ,
Try Below Workarounds:
Workaround 1:
Open Central Admin
àApplication Management à
Configure Alternate access mapping-->Edit your web application zone and add your server name in Intranet zone. So default can be serverIP and intranet could be servername.
Workaround 2:
Might be there is some issue with DNS and try to check that WebApplication is pointing to correct IP or not.
Also try to access your Sharepoint site using ip Address .. If you still gets error Kindly share the logs ..
Best
Regards Kuldeep Verma
Please remember to click "Mark As Answer"
if a post solves your problem or "Vote As Helpful" if it was useful.

Web cache and SSL certificates

We just installed Oracle9iAs 9.0.2.3 on 2 separate machines. All the components have been set up to use SSL and HTTPS protocol and are working fine.
On the mid-tier server we are having a problem where the web cache is throwing up the network error page every time the mid-tier apache home page is invoked or Portal home page is invoked. After a few refreshes the page is ultimately displayed.
I was told that we need a real valid certificate to avoid this issue between web-cache and apache server.
Has anyone created self-signed certificates for their test machines apache server?? What software or method was used to create self-signed valid certificates for test purpose?

Whenever I try to go to the portal home page The web cache is simply displaying the default network error apology page, which says, 'No response from the Application server' in big red. I have to refresh the page a few times to display the portal home page. And this happens a few times when I am browsing through the portal pages too.

Reading data from App Web List and Displaying in HostWeb.

Hi,
Is it possible to read list data from AppWeb and display it on a page in HostWeb?
Any approaches to achieve this?
Regards,
Rivin Jose.

Hi Rivin,
There seems no need to query an app web from host web cause App for SharePoint is designed to work as an “advanced web part” solution, it should work as a separate
component of a SharePoint site which shouldn’t be taken care on the host web side.
If you simply want to display data from app web in the host web, add an App Part into a page in the host web would be the best option for you as what Dan suggests.
Thanks
Patrick Liang
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Web Cache and cookies - need to understand a bit more!

FROM THE ORACLES DOCS
If a document contains a cookie, then Oracle Web Cache evaluates the cookie value of the browser request and application Web server response. If the values match and there is a corresponding cacheability rule, then Oracle Web Cache caches the response. Because a session value change does not necessarily indicate a change of state on the application Web servers, session cookie values are not evaluated. For documents that use these cookies, the response is cached, regardless of whether or not the cookie values match.
OK so does this mean that if I have a site that has a single persistent cookie that say contains the username and the cookie is global over the site i.e. its set for the root "/" then inheritently WebCache cannot cache any page on this site even if the cacheability rule make no mention of cookies as the request and response cookie will be different ie user "bill" goes for first page and WC caches it then user "larry" asks for a page and becuase the request cookie is "larry" and the response is "bill" then it wont cache it even though this particular pages content may make no use of the cookie value.
Also does it mean that if I have a session cookie say for "authenticated" even if I have expressed that the cookie be used to cache different version of the page its no use WebCache will ignore it and simply cache one version for all even though this particular page maybe be different for authenticated and non authenticated users.
Sorry but its not clear just how WC works with cookies.
Thanks for any assistance
Rob

I asked one of the developers about this and here is the
response:
"I think he was not clear on 2 points:
1) we do not store any "Set-Cookie" header from the response.
all such headers are stripped when the document is inserted;
2) cookie comparison is only performed when we receive a response
from the os. On cache hits, no such comparison happens -- we
don't have anything to compare against as the cached documents
never contain any Set-Cookie headers
So in his example, after the response to Bill's request gets
cached (it's cached only when the non-session cookies in his
request and response match), Larry's request for the same URL
will get the cached document WITHOUT the "Set-Cookie" header. So
Larry gets a cache hit and his cookie will not get overwritten by
Bill's.
Now in 9.0 (the upcoming release), the cookie value comparison
only happens for multiversion cookies. So we are relaxing a bit
in that sense and will cache more documents than before.
As for his second part of the question (the authentication cookie
part), I'm not sure what exactly is the application behavior. Do
only authenticated users have the session cookie? If that's the
case, then, he can define a session caching rule to say "cache
with session, and cache without session, and the 2 versions are
different" (3 YES' on the 3 session definition questions). Then
we'll cache a version for the authenticated users (with session)
regardless of the session value, and another version for the
non-authenticated users(without session).
If, however, both authenticated and non-authenticated users have
the same session cookies with different values, and all
authenticated users map to one version of the doc and all
non-authenticated users map to another, then Web Cache can't
currently handle this. This is basically a multiversion cookie
rule, with some grouping of cookie values, which we don't support
yet."

Oracle Web Cache and OBIEE 11g

Anyone using Oracle Web Cache with OBIEE 11g?
Can I get an insight into whether this solution is beneficial? Or I shouldn't even bother.

No iam not using oracle web cache
Can I get an insight into whether this solution is beneficial? Or I shouldn't even bother.I dont have idea about it,but i think its not beneficial ,anyways there is OBIEE cache that is more than sufficient.
hope answered your question.
Cheers,
KK

Web cache and open connection count?

Hi,
I can get a count of the number of open connections through the webcache admin screen.
Is there a piece of sql i can run in sqlplus to provide me with the same information?
Thanks,
Giles

Hi,
There is an option to send a XML message to the Statistics port & get a XML reply giving the Statistics details you had requested for.
Refer on how to do this here :
http://download-west.oracle.com/docs/cd/B14099_02/caching.1012/b14046/invalidate.htm#i1007387
this page is actually for Invalidation request. Similar thing must be done for statistics request, except that you need to use the statistics port instead of the invalidation port.
They have also said how to use database triggers for the same:
http://download-west.oracle.com/docs/cd/B14099_02/caching.1012/b14046/invalidate.htm#sthref1878
You can get the Statistics DTD from here:
http://download-west.oracle.com/docs/cd/B14099_02/caching.1012/b14046/dtd.htm#sthref2538
Hope this helps.
Thanks & Regards,
Priyanka GES

Cannot start Web Cache in Oracle 10g App Server

Hi,
Our Application runs on Oracle10g App Server,
When it tried to start WebCache using the command
opmnctl startproc ias-component=WebCache process-type=WebCache
it shows the error...
opmn id=oracle10g:6200
no enabled components for this request
When i tried to enable WebCache using Enable/Disable Component in Oracle 10g Enterprise manager - I can't see WebCache component it to enabe or disable it.
When i tried opmnctl status., it shows
------------------------------------------------+---------
ias-component | process-type | pid | status
------------------------------------------------+---------
HTTP_Server | HTTP_Server | 7276 | Alive
LogLoader | logloaderd | N/A | Down
dcm-daemon | dcm-daemon | N/A | Down
OC4J | home | 7684 | Alive
OC4J | rhs | N/A | Down
OC4J | instaremit | 5880 | Alive
OC4J | insta_test_apr_02 | 7100 | Alive
WebCache is not running, also as the WebCache is not listed in Oracle 10g Enterprise manager, i can' enable or disable it.
Plz Help me over this.,
Regards.,
Deepak.C

Hi.,
Thanks again !!!
Yes, My Oracle HTTP Server is listening on port 80.
I am not clear, may i know why should the ports be changed for the request to go through Web Cache ???
Can i assign port 80 for Web Cache and 7778 for HTTP Server ?
Also In Oracle Enterprise Manager, Web Cache is not available...
home, HTTP Server, management alll these are there...
Also for HTTP Server, it's not showing any metric info, 'Not Yet Available' is shown even though the HTTP Server is running, how can i get metric info about Oracle HTTP Server, i have also used dmstool -t ohs_server, its not working
It's showing... FLEXMON ERROR : detected invalid table name ohs_server
dmstool -l -t also does'nt lists ohs_server
Hellp me over this.....
Deepak.C

Forms/Reports: Role of the Database cache and Web cache

Hello oracle experts,
I am running a purely Forms and Reports based environment (9iAS).
My question are:
a. Is it possible to use features from the Web Cache and
Database Cache to boost the performance of my applications?
b. Are all components monitorable from the OEM?
Please guide me so that i can configure my OEM to monitor my
forms and reports services.
thanks in advance for your reply
Kind regards
Yogeeraj

Hi BradW,
The way this is supposed to be done in Web Cache is by keeping separate copies of a cached page for different types of browsers distinguished by User-Agent header.
In case of cache miss, Web Cache expects origin servers to return appropriate version of the page based on browser type, and the page from the origin server is just forwarded back to browser.
Here, if the page is cacheable, Web Cache retains a separate copy for each type of User-Agent header value.
And when there is a hit on this cached page, Web Cache returns the version of page with the User-Agent header that matches the request.
Check out the config screen titled "Header Association" for this feature.
About forwarding requests to different origin servers based on User-Agent header value, Web Cache does not have such capability.

Web Cache Error

We are occassionally getting the following error in various scenarios -- in development or just browsing the site:
"Oracle Web Cache Network Error"
Oracle Web Cache encountered a network error when communicating with the application web server.
We have Web Cache installed on the same server as the portal application, but an Oracle consultant who was in a few weeks ago said we had more than enough capacity. Any ideas? We're on Oracle Portal Version: 3.0.9.8.2 and

The error you are seeing is usually the result of a slow response from your origin server, although it could be something else. If you provide
a snippet of your Web Cache event log (verbose), I'll be able to assist you better.
For now, let's assume it is due to a slow origin server response. On a cache miss, if the Web Cache doesn't receive a response
from the origin server within a given time interval, it will close the connection with the origin server and respond to the browser with
a network apology page. This is the page you are seeing. There are ways to correct this.
First of all, you should modify the network apology page in order to customize it for your application or web site. The file is located in the $ORACLE_HOME/webcache/docs directory.
If you're using Web Cache 9.0.2.x, the default origin server timeout is 3600 seconds. You probably won't have to change this, but if you want to, then
please refer to the "Oracle9iAS Web Cache v9.0.2.0 Administration and Deployment Guide", available on OTN.
The relevant section is" Chapter 6, Task 7: Configure Network Timeouts."
If you're running Web Cache 2.0.0.x, the default origin server response timeout is 30 seconds. This default was chosen because we felt
that no application should take more than 30 seconds to respond to a user's request. Since then, we've learned that a lot of apps out there,
especially business intelligence apps, have complex queries that take several minutes, if not hours, to complete. To change this default timeout, you need to modify your internal.xml
file. Here's a snippet from the 2.0.0.4 readme.html file describing how to do this:
3.0 Network Apology Pages
When Oracle Web Cache sends requests to an application Web server, Oracle Web Cache permits the application Web server 30 seconds in which to
generate a response for the browser. If the application is unable to generate a response within that time, Oracle Web Cache sends a network apology
page to the browser.
If 30 seconds is not sufficient, then you can change the default settings of the OSSEND_TIMEOUT and OSRECV_TIMEOUT attributes in the
internal.xml file:
OSSEND_TIMEOUT: Network round-trip time (latency) between Oracle Web Cache and the application Web server. The 20 second default of
the OSSEND_TIMEOUT attribute is usually sufficient for most operating systems.
You can determine the latency to the application Web server by issuing the the following command from the Oracle Web Cache computer:
ping -s application_Web_server
This command provides output similar to the following:
PING sales.us.acme.com: 56 data bytes
64 bytes from sales.us.acme.com (130.35.45.34): icmp_seq=0. time=20. ms
64 bytes from sales.us.acme.com (130.35.45.34): icmp_seq=0. time=21. ms
If the time value is over 20 seconds, then increase the OSSEND_TIMEOUT attribute value.
OSRECV_TIMEOUT: Latency and application Web server processing time. The default is 30 seconds.
You can determine the processing time by sending a sample request to the application Web server and monitoring the time to process the
request. If the processing time is over 30 seconds, then increase the OSRECV_TIMEOUT attribute value.
To change these default settings:
1.Locate the following line in the internal.xml file:
<CALYPSONETINFO/>
2.Modify the <CALYPSONETINFO/> line as follows:
Add the OSSEND_TIMEOUT attribute as follows:
<CALYPSONETINFO OSSEND_TIMEOUT="seconds"/>
Add the OSSRECV_TIMEOUT attribute as follows:
<CALYPSONETINFO OSSRECV_TIMEOUT="seconds"/>
Add both the OSSEND_TIMEOUT and OSSRECV_TIMEOUT attributes as follows:
<CALYPSONETINFO OSSEND_TIMEOUT="time" OSRECV_TIMEOUT="time"/>

How I now if Web Cache is working??

I can access the Oracle Application Server Control Manager and I can see the Web Cache Component running.
Now, I go to jesi_template.jsp demo to see if my Web Cache is working, but when I refresh the page, the date and time is equal in jesi_template.jsp and ESI Fragment.
I have my Web Cache and Application Server in the same server (host).
My question is: Is this correct? or the dates and times would have to be different?

http://www.islayer.com/apps/istatpro/

Using Web Cache to Load balance Forms Server application.

Hello,
I apologize for cross posting this question in the Forms and Caching Services forum. But I thought my question will have a better chance.
I have read that it's possible to use Oracle Web Cache as a software load balancer between multiple Application Servers.
We are running Oracle9iAS R1.0.2.2.2a, with Forms/Reports6i servers on 2 Win2k boxes i.e our Forms6i application is deployed on two seperate boxes in two distinct locations. Users at each location, use their respective App Server url.
Since the application is the same i.e. Forms6i code/fmx is the same for both locations, I am looking into loadbalancing and failover capability that Web Cache might be able to provide.
I AM ONLY LOOKING AT THE LOADBALANCING & FAILOVER capabilities and NOT caching.
So basically all users from both locations will point their browser to this Web Cache and the Web Cache will direct each connection to either of the two boxes. So, if either of the boxes dies, Web Cache will divert the requests to the other box.
My concern is whether Web Cache supports this for the Forms requests that it will receive from the users. We are using Servlet Deployment of Forms, so technically, all communication is going though the HTTPD.
Has anyone done this or has any ideas as to whether it's going to work or not? Oracle's FAQ insists that Forms is not supported. But I want to make sure that even loadbalancing is not supported. And if not supported then is there any other solution.
Any comments appreciated.
Thanks,
Manish

Using Web Cache to load balance servlet-based Forms (6i and 9i) is unofficially supported. I say "unofficially" because we have actual customers doing it and getting support, but the 2 development teams (Forms and Web Cache) haven't actually done any integration testing of this sort of configuration yet. For your case, please contact your Support rep and ask what was done to use Web Cache as a load balancer for Forms6i at METRO in Germany. The Forms product managemment team is writing up a white paper to describe how to do it, but until then, you'll need to go through Support. Please contact me if you want more information.

Forms6i Server (9iAS R1.x) loadbalancing using Oracle Web Cache

Hello,
I have read that it's possible to use Oracle Web Cache as a software load balancer between multiple Application Servers.
We are running Oracle9iAS R1.0.2.2.2a, with Forms/Reports6i servers on 2 Win2k boxes i.e our Forms6i application is deployed on two seperate boxes in two distinct locations. Users at each location, use their respective App Server url.
Since the application is the same i.e. Forms6i code/fmx is the same for both locations, I am looking into loadbalancing and failover capability that Web Cache might be able to provide.
So basically all users from both locations will point their browser to this Web Cache and the Web Cache will direct each connection to either of the two boxes. So, if either of the boxes dies, Web Cache will divert the requests to the other box.
My concern is whether Web Cache supports this for the Forms requests that it will receive from the users. We are using Servlet Deployment of Forms.
Has anyone done this or has any ideas as to whether it's going to work or not?
Thanks,
Manish

Manish,
we tested this but came across problem with Webcache that have to do with the jsession Forms uses. This is fixed for Oracle9iAS 9.0.2.x. So if you want to run Forms with Webcache in front, then please do this using the latest version of Oracle9iAS V2 Webcache. For Oracle9iAS V1 and Forms Services we recommend not to use Webcache but do the load balancing via JServ.
Frank

Oracle Web Cache - Load Balancer Mode

Hello,
I am facing a problem related to fault tolerance in Oracle Web Cache
My environment:
2 Nodes of Oracle Application Server 10.1.3 configured in cluster.
have configured Oracle Web Cache (in LoadBalancer mode only) to simulate a BigIP load balancing above these two oc4j node. This to be used as fault tolerance so if one http request will fail the LoadBalancer will direct it to the second oc4j (its http server).
I have used the defaults recommended by Oracle documentation for configuration clustering load balancer using Oracle Web Cache and using JSESSIONID for Session binding with oc4j-type. I left all other cluster/server setting to default
Problem:
The problem is when I am shutting down one oc4j instance the Oracle Web Cache tries to keep the session with the un-available oc4j node and not direct the session to the other oc4j node.
If I choose to start a new session (loose current work) than it does work with the second (alive) oc4j node, but than where is its fault tolerance??
What do i need to do to keep working with the same session over the second oc4j node. My deployed Web App is enabled to work in cluster, using Oracle Application Server console. Here is its orion-application.xml
+<?xml version="1.0"?>+
+<orion-application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://xmlns.oracle.com/oracleas/schema/orion-application-10_0.xsd" deployment-version="10.1.3.1.0" default-data-source="jdbc/OracleDS" component-classification="external"+
schema-major-version="10" schema-minor-version="0" >
+     <web-module id="session_rep" path="session_rep.war" />+
+     <persistence path="persistence" />+
+     <principals path="principals.xml" />+
+     <jazn provider="XML" />+
+     <log>+
+          <file path="application.log" />+
+     </log>+
+     <cluster allow-colocation="false">+
+     <replication-policy trigger="onRequestEnd" scope="modifiedAttributes"/>+
+     <flow-control-policy enabled="false" />+
+          <protocol>+
+               <peer>+
+                              <opmn-discovery/>+
+               </peer>+
+          </protocol>+
+     </cluster>+
+</orion-application>+
Will appreciate any help !

is OHS/apache deployed between web cache and your OC4J? if so, i think since OHS/apache is alive to web cache, web cache keeps routing to it.
maybe in your script, you can shutdown both OHS/apache and OC4J totgether so web cache can correctly route.

Can Web Cache rewrite HTTP_REFERER headers?

Can Web Cache be configured to rewrite the HTTP_REFERER header to replace the Web Cache site address:port with the dispatched application server address:port?
i.e.
If there is a Web Cache site listening on webcache.domain:80 and it is mapped to application servers: appserver1.domain:7778 and appserver2.domain:7778.
And a user requests page webcache.domain/page1, which contains a link to page2.
And then the user opens the link to page2, and Web Cache decides to send the request on to appserver2.
Can Web Cache be configured to change the HTTP_REFERER header from webcache.domain/page1 to appserver2.domain/page1?
This is important to our application, because we want to verify that our processing pages are invoked from our application validation pages (we know this method is not 100% tamper proof).
We would prefer to not have to change our application code to support Web Cache
Thanks for any info or suggestions, -Steve

Thanks Jean
I've added comments to extracts from your post.
Let's say you suddenly get a request for p2, even if
it was from the history of the browser, it would still
contain a referer header of p1, and is no different
from what it would be when the user was going through
the proper steps? Are you saying the p2 generated from
your JavaScript will have a different referer from the
p2 generated from browser history? If so, how are they
differ exactly?The browser history does not include the referer. So p2 requested from the history list does not include a referer although the original link from p1 did.
Without Web Cache, the flow is:
Step 1: a user requests appserver/page1. page1 is added to the browser history. page1 is loaded and executes JavaScript to display page2 in an iFrame. page2 is not added to the browser history (just like style sheets and other embedded requests do not get included in the history). page2 is loaded and executes JavaScript to submit an html form to load page3 into a hidden iFrame and wait for it to load. page3 is added to the browser's history becuase it was submitted; not embedded. Assuming that the request for page1 came from the browser's history, favorites, a link from an e-mail (the usual for us), or was entered manually - there will be no referer for page1. The expected referer for page2 is appserver/page1, and the expected referer for page3 is appserver/page2.
Step2: while processing page3, the application compares the server name in the requested URL (appserver/page3) with the server name from the referer URL (appserver/page2), if the servers match, page3 accesses the database and sends the requested data to the browser
Step3: JavaScript in page2 detects that page3 has loaded, interprets the results from page3, updates the content displayed by page2, and returns control to the browser user
Since this works with your app, how is webcache in
front going to break it? Note that when passing a
request
to the app server, web cache does not modify the
host header in the request.without Web Cache the browser sends requests directly to the appserver, so the request/referer entries seen by the application look like:
appserver/page1 -
appserver/page2 appserver/page1
appserver/page3 appserver/page2
with Web Cache the browser sends requests to webcache, so the request/referer entries seen by the application look like:
appserver/page1 -
appserver/page2 webcache/page1
appserver/page3 webcache/page2
This is because the Web Cache changed the request URL and did not change the referer URL.
So request to webcache.domain/abc will be sent to your
app server as is.I don't think so, doesn't the requested URL change as a result of the Web Cache mapping? i.e. webcache.domain/abc --> appserver.domain/abc
And since we do not change the referer
header, either, whatever works for your app now should
still work for you with webcache in front. This is
assuming you only do comparisons on the 2 hosts to see
if they are the same. Web Cache is changing one (request URL) of the two items (request URL and referer URL) that the application server compares.
The reason has been that we are
a cache, and in principal should be as transparent
as possible, so we try to stay away from app-sever/
apache like functionality.I support that principle 100% - from the application server perspective, it should not need to differentiate between a request directly from a browser, and a request that was issued by the cache on behalf of a browser.
The cache should completely pretend that it is the originating browser. A browser sends the request and the referer URLs. In application flow, a relationship can be inferred/required between the two URLs. Web Cache is changing one without changing the other and breaking the relationship that the application server would normally expect.
But I'm still
not convinced that you need that in webcache. :)If we want to use Web Cache in front of this application, without changing the application, then we need it. :)
Of course, we could change our application, but the more I think about the principles involved, the more I believe that it is the cache that needs changing. However, I will take another look to see if there are other standard headers related to a request that are present with and without Web Cache, and that can be used to reliably compare the server in the request URL with the server in the referer URL. If there are, then I can happily change our application so that it will work with or without Web Cache.
-Steve

Sample app: Web Cache and ESI

Similar Messages

Maybe you are looking for