Report instance view runs slow

[Former Member]

I am just starting to migrate Crystal reports into BOE XI R3, using the CMC to add the reports from the file system. With each new report, I create a recurring schedule and a run-now instance.

The first four reports performed well. The fifth seemed to hang the browser when viewed. I eventually found the process (View Latest Instance or view from History) would complete in about 15 minutes. At about 12 minutes, IE generates a message:

A script on this page is causing Internet Explorer to run slowly. If it continues to run, your computer may become unresponsive. Do you want to abort the script?

The CMC/browser status line shows it is trying to open crystalreportviewers / htmlbridge.jsp.

The instance takes about 1 minute to run in the CMC. The report uses about 60,000 records and produces about 4,500 pages.

In Crystal Enterprise 9, our current platform, the same instance is viewable in 2-3 seconds.

The first four reports migrated to XI3 run in less than a minute and are viewable in 5-6 seconds, have from 120 to 6,400 pages, and use the same dataset.

Not seeing any significant differences between the quicker and slower reports, I'm at a loss as to where BOE is failing. I'd appreciate some thoughts. Thanks!

[former_member145588 · Accepted solution]

Hello,

If your looking for way to improve performance for the infoview please review 1292411 - How to Improve the performance of Infoview in XI R3. Below is the resolution from that SAP note. I hope this resolves your issue.

Enable browser caching

Backup the exising web.xml <deploymant folder>\InfoViewApp\WEB-INF\web.xml (where deployment folder is the location the applications that have been deployed in your environment)

Open the web.xml file and search for the text :

<init-param>

<param-name>nocache</param-name>

<param-value>true</param-value>

</init-param>

modify the line <param-value>true</param-value> to <param-value>false</param-value>

save the file

restart your web application server

If you are using Secure Sockets Layer on Tomcat Application server then follow these instructions

Backup the exising context.xml <path to>\tomcat\conf\context.xml (where path to is the location where tomcat is installed)

Open the context.xml file and add the text:

<Value className="org.apache.catalina.authenticator.FormAuthenticator" disableProxyCaching="false" />

save the file

restart Tomcat

[Former Member · Accepted solution]

Thanks, Jorge. My searches had not found note 1292411.

After the holiday and a 3-day class, I was able to try your suggestion. Unfortunately, the behavior is still the same. Any additional ideas would be appreciated.

[former_member145588 · Accepted solution]

If you have page n of m field on the report try removing it from the report. Once that is completed then try and view the report again. See if that resolves the issue.

[Former Member · Accepted solution]

Thanks again. but I'd already had that suggestion. Unfortunately, the other reports also use Page n of m with no problem - and just as many pages. Still, I removed n-of-m and from this one problem child and it still takes 12+ minutes to display the first page.