The reports mechanism consist of the following components:
- Oracle Views
- Mapping table
- BIRT Viewer
- BIRT Files (*.rptdesign)
- BIRT Library (*.rptlibrary)
- Reports deploy directory
A mapping table named Birt Management Reports defines which of the reports will be accessible at each of the ‘Run Reports’ menus and the name and description for each report.
BIRT Report Designer: BIRT is an open source application, installed on the application server, used to generate the reports in real-time. BIRT can be downloaded at http://www.eclipse.org/birt/. In order to create a BIRT report that can be implemented in Rosetta, download Eclipse Birt 4.5.0 (the latest BIRT version supported as of Rosetta 5.0).
Note: This package does not include an Oracle JDBC driver, which you will need to connect to Rosetta. This driver can be copied from the Rosetta server ($dps_dev/system.dir/thirdparty/tomcat/lib/oracle*.jar). Instructions on how to add the jar to Eclipse are provided here (under ‘JDBC Drivers’).
The BIRT library is an XML file, used for storing technical information that is used by all the reports (*.rptdesign), e.g. DB connection string, styles etc.
All *.rptdesign and rptlibrary files are located at $dps_dev/system.dir/thirdparty/tomcat/rosetta-webapps/dps-report-web.war/report. When setting up your BIRT environment you will need to copy your library file as a shared resource so that all reports can use this as a data source.
Completed report files (rptdesign) should be copied to this location (on each REP server).
After placing the rptdesign file on the server(s), add them to the relevant backoffice menu (Producer, Submission, Data Management, Preservation) using the BIRT Management Reports mapping table:
See also: Adding a BIRT Report to Rosetta.