In the discussion about enabling web cache for Discoverer Viewer, in the first paragraph on the top of page 803, I state "This is why Oracle explains you must cache only Discoverer Viewer content delivered through a Discoverer Public connection".
This needs to be qualified because you can ONLY enable web cache for Discoverer Viewer when delivering content through a Discoverer Public connection. This is stated quite plainly in the latest 10.1.2.0.2 documentation. However, the 10.1.2.0.0 documentation did not say this and you might be fooled, as I was at first, into thinking that there had been a change of functionality in the latest 10.1.2.0.2 release. Happily, this is not the case because even in 10.1.2.0.0 you must be using Public connections, and therefore an Infrastructure database, in order to cache Viewer content.
What this means in plain talk is that if your company installs only the stand-alone version of Discoverer Viewer you cannot use web cache for caching frequently used pages. Now I know some of you will say that even in a stand-alone version of Discoverer you can turn web cache on using OEM. This is true. However, Discoverer will ignore this setting until it detects that Public connections are in use. It makes sense really when you think about it because you don't want private data being cached and inadvertently displayed to someone who should not see it.
I hope this explanation helps.
Usability, Product Management, and LinkedIn - a rant - L inkedIn began as a professional networking site, has evolved into a social media behemoth, and has yet managed to maintain and sharpen its focus on the p...
3 weeks ago