When using SSLConfigTool to reconfigure a HTTP portal ( 10.1.4 ) to listen to your external HTTPS adres. You might run into this error while requesting your default welcome page in portal. In my case i like to have 2 seperate external names for portal to listen too.
So here is what i did :
Create a file for each external adres to be configured by SSLConfigTool.
Under “/home/oracle/scripts/” i created a file “portal.it-eye.nl.cfg” for one of the external adresses “portal.it-eye.nl” which look like this;
<SSLConfig>
<mid_tier>
<virtual_address ssl="on" host="portal.it-eye.nl" port="443" inv_port="9401" ssl_terminate="lbr"/>
<lbr loopback_port="7778"/>
<wc/>
<ohs>
<servers>
<server host="portal.iteye.local" port="7779" />
</servers>
</ohs>
</mid_tier>
</SSLConfig>
Loopback_port ( 7778) = Webcache port which portal is using
Server port (7779) = http server port which portal is using
Inv_port ( 9401) = invalidation port which portal is using
( All these ports van be found from your AS console, under ports )
Virtual address port (443) = external port for .nl / testmijn.das.nl
You can then process this file by running the SSLConfigTool like :
[oracle@portal bin]$ ./SSLConfigTool -config_w_file /home/oracle/scripts/portal.it-eye.nl.cfg -ptl_inv_pwd <orcladmin_password> -opwd <orcladmin_password>
After running the SSLConfigTool for both external addresses. I was not able to reach one of the external address, as this would result in the following error “The XML page cannot be displayed”.
As of this point i was not sure where to find the solution for this strange error. While checking the webcache configuration i found one external address missing here. I was sure this would be taken care of by the SSLConfigTool as this step was succesfully processed as shown in the configuration log.
After manually adding this entry i was able to reach my default welcome page in portal again.
(https://portal.it-eye.nl/portal/page/portal/TOPLEVELSITE/Welcome)
Background information on this is that the Oracle Portal was not configured correctly using webcache and therefor not responding in the correct way.
Since Portal 10.1.4 relies on ESI technology, the response from the OHS Port is an XML file which is displayed
as-is in the browser. If this XML was correctly accessed thru WebCache, then WebCache would have processed the XML to return a Portal page.
