Last updated on FEBRUARY 28, 2013
Applies to:Oracle Discoverer - Version 10.1.2.1 to 10.1.2.3 [Release 10.1.2]
Information in this document applies to any platform.
***Checked for relevance on 28-Feb-2013***
- When a Discoverer session (Plus or Viewer) is started over a VPN connection (similar to 'intranet') as an HTTP request, Discoverer behaves as expected and launches properly.
- When a Discoverer session (Plus or Viewer) is started over a non-VPN connection as an HTTPs request,
- the initial Discoverer connect page loads (https),
- the'Connect To' is changed to 'Oracle Applications' and at that point it errors with: "Page cannot be displayed"
The architecture includes Discoverer and Web Cache 10.1.2.0.2 fronted by a BigIP router using an SSL accelerator.
- Internal requests over a VPN connection are processed by BigIP using http protocol.
- When an external request is submitted without VPN connection, the initial URL is an https request.
- BigIP uses an SSL accelerator to "strip off" the SSL request and forwards the session to Oracle WebCache as http
- WebCache then forwards the request to a backend Discoverer BI server.
The key symptom in this environment can be identified by observing the HTTP Header traffic with one of two third party browser plugins for Microsoft Internet Explorer:
- IEWatch -- http://www.iewatch.com (preferred for ease of readability)
- ieHTTPHeaders -- http://www.blunck.se/iehttpheaders/iehttpheaders.html
Once you are at the connection page and attempt to connect, if you see the traffic direct from HTTPS >> to HTTP >> then back to HTTPS where the 'Page Not Found' failure occurs, then you will need the solution below.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms