BO SDK Implementation Using Java Reporting Component.

POC(Proof of Concept).

The POC (Proof of Concept) is to demonstrate the capabilities of Business Objects XI R2 &
BO SDK Programming tools along with Java Reporting Component to satisfy the business
needs.

The POC has been framed in such a way it will describe the usage of Business Objects XI
R2, Java Reporting Component (JRC) & JSP.

A Webpage calls a BO Crystal Report through the Info view. Webpage Logs into BO and
passes certain (not all) parameters. These parameters cannot be modified/seen by the
user.

The functionality demonstrated by this POC will allow users to seamlessly access BO
reports and the option to Export the data to various formats including Comma Separated
Values (CSV).
Solution Overview

Crystal Reports Java Reporting Component includes the Java Reporting Component and a
version of the Viewer Java SDK. The Java Reporting Component is an embedded reporting
solution that processes reports for viewing and exporting. The Viewer Java SDK allows you
to develop web applications that can both display Crystal reports and export them to other
formats.
The viewers can use the Java Reporting Component to obtain a report source and then
display the report associated with the report source.

-1-
 • BO SDK API.
Software
• Java application server.
• Business Objects Application Framework.
• Viewer Java SDK.

The benefits that the POC highlighted can be summarized as

Business Benefits

ƒ Service oriented reusable operational reporting interface

ƒ Reduced cost for future projects.
ƒ Help the end users with export to multiple formats like (CSV, EXCEL).

Technical Benefits
BUSINESS OBJECTIVE

ƒ Integration of a web application with Business Objects.

ƒ Crystal reports provide an easy interface for the end users, so pagination will be
simpler.
ƒ To demonstrate that BO can have security integration with web applications and
portal applications without having to load the individual agents into BO.
ƒ If we're not doing row-level access control with the BO user ID, then we need to
demonstrate that the user cannot change the query like they can in WEBI Report.
ƒ To demonstrate that we can encrypt search parameters from end-users so they
cannot hack or manipulate the reports.
ƒ If we use the SDK approach rather than the Customization of the interface, we
need to demonstrate that we still have the capability to
Download as a CSV file.
Download as a PDF file.
Download as an Excel spreadsheet.

Objective of this application is the integration of a webpage with the Business Objects
application will provide the users with multiple parameters by which data can be
SCOPE

analyzed.

Technical Assumption.

• BO SDK Framework has to be installed.

Web pages have to be build, taking the Crystal report features into
Assumptions

•
consideration.
• Security features has to be implemented in the JSP web pages.
• JDBC Data source has to be configured to use JRC.
• The Target users should be categorized accordingly.
• Ensure JRC functions correctly.

-2-
 The Business Objects Enterprise SDK allows you to build web applications that interface
directly with your Business Objects Enterprise system.
The Java Reporting Component (JRC) enables you to embed report viewing and exporting
into your existing web applications. The JRC provides the Java viewers, which are a
collection of Java classes that can be used to generate HTML and Dynamic HTML pages
that display and export Crystal Reports. For example, you could use the JRC to create a
lightweight reporting application that is embedded directly into JSP pages.
The following export formats are supported by the JRC when exporting server-side using
the 'PrintOutputController' object:
• Portable Document Format (PDF)
• Rich Text Format (RTF)
• Editable RTF
• Crystal Reports (RPT)
• Character-Separated Values (CSV)
A powerful feature that the Java viewers provide is the ability to export Crystal report files
to different formats. Reports can be exported to a different format for distribution or for
viewing on a local machine.
Functional Specification

The SDK provides the ability to programmatically export a report in addition to the ability
to export the report through the DHTML viewer.
This table shows the export formats that are supported by the SDK.

Format Type. Export Format.

Client Side.

RTF Rich Text Format

RTF (editable) Editable Rich Text Format

PDF Adobe Acrobat

Server Side.

RTF Rich Text Format

RTF (editable) Editable Rich Text Format

PDF Adobe Acrobat

CSV Character Separated Values Format

-3-
 The Java Reporting Component classes provide you with the ability to process reports for
Technical Specification viewing and exporting.

Example Java Reporting Component In-built Packages.

com.crystaldecisions.reports.sdk: This package is used to provide access to a report

and its data sources.

com.crystaldecisions.sdk.occa.report.exportoptions: This package allows you to

specify the export format of a report document.

Java Reporting Component SDK:

http://devlibrary.businessobjects.com/businessobjectsxir2/en/devsuite.htm#en/JRC_SDK
/jrc_java_dg_doc/doc/jrcsdk_java_dg/BestPractices.html
For various Exporting Options in JRC:
http://technicalsupport.businessobjects.com/KanisaSupportSite/search.do?cmd=display
KC&docType=kc&externalId=c2018302&sliceId=&dialogID=11764473&stateId=1%200
%2011768157
References

SDK Over View Diagram:

http://devlibrary.businessobjects.com/businessobjectsxir2/en/en/general_doc/SDKOvervi
ew_Final_EN.htm
IBM on Java Reporting Component:
http://publib.boulder.ibm.com/infocenter/rtnlhelp/v6r0m0/index.jsp?topic=/com.busines
sobjects.integration.eclipse.doc.devtools/developer/ReportingJRC.html

-4-