Fixes for IE9 with XI3.1 SP3
Note: this should work for *nix as well as Windows if you are using a JSP/Tomcat deployment
Known issues wrote:
Known issues:
When attempting to Pause/Resume a recurring instance, via Actions drop down Pause, a blank page is displayed.
Step 1 - Build the redirect page for InfoViewAppActions.
To catch the errors that occur in the InfoViewAppActions application, open that directory. On windows machines the path is:
Path on Windows wrote:
C:\Program Files (x86)\Business Objects\Tomcat55\webapps\InfoViewAppActions
You will see existing error catch files in this directory called httperror_404.htm and httperror_500.jsp
unzip the attached file and copy httperror_400.htm & httperror_404.htm from the InfoViewAppActions folder in the zip file and place them here with the others.
Note: You need to be logged into the forum to see attachments
Step 2 -Catch the errors (400 & 404) by editing the web.xml file for InfoViewAppActions.
On windows machines the file is here:
Path on Windows wrote:
C:\Program Files (x86)\Business Objects\Tomcat55\webapps\InfoViewAppActions\WEB-INF\web.xml
The web.xml file has already been setup to catch error 404 & 500. We need to tell Tomcat to use our redirect page when it detects an error 400 as well.
At the bottom of the file, you will see traps for error 404 and 500. We need to set one up for error 400, so change
Code:
<error-page>
<error-code>404</error-code>
<location>/httperror_404.htm</location>
</error-page>
to
Code:
<error-page>
<error-code>404</error-code>
<location>/httperror_404.htm</location>
</error-page>
<error-page>
<error-code>400</error-code>
<location>/httperror_400.htm</location>
</error-page>
Step 3 - Build the redirect page for AnalyticalReporting.
There are also redirect issues when viewing the status of scheduled instances, these occur in the AnalyticalReporting application.
To catch the errors that occur in the AnalyticalReporting application, open that directory. On windows machines the path is:
Path on Windows wrote:
C:\Program Files (x86)\Business Objects\Tomcat55\webapps\AnalyticalReporting
You will see existing error catch files in this directory called httperror_404.htm and httperror_500.jsp
unzip the attached file and copy httperror_400.htm & httperror_404.htm from the AnalyticalReporting folder in the zip file and place them here with the others.
Step 4 -Catch the error (400) by editing the web.xml file for AnalyticalReporting.
We need to tell Tomcat to use our redirect page when it detects an error 400. We do this using the web.xml file.
On windows machines the file is here:
Path on Windows wrote:
C:\Program Files (x86)\Business Objects\Tomcat55\webapps\AnalyticalReporting\WEB-INF\web.xml
At the bottom of the file, you will see traps for error 404 and 500. We need to set one up for error 400, so change
Code:
<error-page>
<error-code>404</error-code>
<location>/httperror_404.htm</location>
</error-page>
to
Code:
<error-page>
<error-code>404</error-code>
<location>/httperror_404.htm</location>
</error-page>
<error-page>
<error-code>400</error-code>
<location>/httperror_400.htm</location>
</error-page>
Step 5 - Restart Tomcat to refresh the application and test with IE9
Partager