When we turn on SiteMinder, our jsp pages (using Struts, for example logon.do) return error “This Page Cannot be Displayed” as if it doesn’t exist. As soon as we turn SiteMinder off, these pages display. Does anyone know what would make this happen?
https://dns/businessobjects/enterprise11/admin/en/admin.cwr (here I am prompted for username/password for SiteMinder then I get the error this page cannot be displayed). Any help would be greatly appreciated, as we are working against a tight deadline.
https://dns/businessobjects/enterprise11/admin/en/admin.cwr (here I am prompted for username/password for SiteMinder then I get the error this page cannot be displayed). Any help would be greatly appreciated, as we are working against a tight deadline.
If it is XI R1 you need a hot fix as we had similar issue. but if it is R2 then im not sure.
In R1 the appletpopup.jsp has an area where it is hardcoded to HTTP rather than being automatic. So it is not able to recognize HTTPS.
The hotfix will make it automatic.
To make sure thats the issue search in the desktop.war for appletpopup.jsp and see how the protocol is and if it is hardcoded then apply the hotfix else im not sure.
I looked at appletpopup.jsp and yes, we are running XI R1. Within the code for the parmater, Protocol, it looks like the following:
‘’
Is this correct?
We had problems before creating a new document using InfoView and found we had to apply a Service Pack. Once we did that, we were able to create new documents. But now, we are having problems displaying pages since we have SiteMinder on. Is the service pack the hotfix you are talking about? If not, can you point me to the location of the hotfix? Thank you for all your help.
after you had the Service pack it fixed the protocol type in the Appletpopup.jsp, so now its pulling up the correct method automatically.
did the articles i mentioned help you?
I’m sorry but I am not sure I see where the article you sent will help me. We applied the service pack about a month ago, which fixed our problem with the universe and creating new reports. See at that time, we only had Siteminder protecting one directory of the website (which wasn’t the business objects directory). Then we found we couldn’t get the header from siteminder in a directory that wasn’t protected (which made sense, should have planned better). So, we changed SiteMinder configurations to protect the entire website. We also have IIS and Tomcat bridged. Thank you for any input you may have, because I am completely stumped on this issue. We have been working at this for 3 weeks.
I removed your duplicate post made about 1.5 hours later. Please be patient, the correct person may not log onto BOB until tonight, tomorrow, or one day next week.
We upgraded to release 2 now. Most of our pages are now being displayed; however, after you login, the next page gives us the same error. This page cannot be displayed. Does anyone else have any other suggestions?