Whether you choose single or multiple report bursting, eventually you will want to deliver the results to your users, and if you are delivering a custom application solution, that means understanding the object model around publications.

A publication object appears in a BOE folder just like a report does, and like a report, it too has historical instances. But whereas a report instance represents a snapshot of the report with data, a publication instance is a container that further holds (you guessed it) the report instances themselves.

The great thing about BOE publication architecture is that the report instances held in a publication instance are automatically filtered to the report instances the currently logged in user has been “bursted.” In other words, it makes no difference if a user has rights to the folder in which the publication resides; he/she must have been named (or at least the user group to which he/she belongs must have been named) as a burst recipient in the publication. » Read more: Business Objects Bursting SDK – Part 2

If you ask the SAP developer support, they will say it’s not supported. However, there are complex Crystal Reports that renders properly in ActiveX viewer.

The only option right now is to use InfoView’s URL reporting. This is ok but there are a few places where this can get you into trouble. For example, let say your J2EE application is on the DMZ and your BOE server is inside of your corporate network. The firewall will only let certain ports (e.g. 6400) and no http requests. In case of URL reporting, you would have to call <BOE server>:<http port>/businessobjects/viewrpt.cwr from your J2EE applications. This will not work. In most cases, opening http port so that ActiveX viewer would work is not an option.

Here’s how to setup URL reporting as a part of you own application.

1)  copy crystalreportviewers folder from infoview /businessobjects/viewers folder and place it in the root of your J2EE application

2)  copy WEB-INF/lib/reportsourcebridge.jar from InfoView application and place it in WEB-INF/lib folder of your J2EE applicaiton

3)  Edit WEB-INF/web.xml to include

<context-param>
<param-name>crystal_image_uri</param-name>
<param-value>/crystalreportviewers115</param-value>
</context-param>

<servlet>
<servlet-name>viewrpt</servlet-name>
<description>
Reportsource bridge used to support Java applet viewer and ActiveX viewer.
</description>
<servlet-class>com.businessobjects.crystalreports.reportsourcebridge.ReportSourceBridge</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>

<servlet-mapping>
<servlet-name>viewrpt</servlet-name>
<url-pattern>/viewrpt.cwr</url-pattern>
</servlet-mapping>

4)  Restart Tomcat

5)  You should be able to access URL reporting from <your J2EE application>/viewrpt.cwr