BIRT 3.7 Runtime Deployment Guide
< To: BIRT/FAQ/Deployment
- 1 BIRT POJO Runtime Overview
- 2 Migration of Older Applications
- 3 BIRT POJO Viewer Deployment
- 4 Engine Deployment
- 4.1 Deploying BIRT POJO Runtime in a Servlet
- 4.2 Deploying BIRT POJO Runtime in a POJO
- 4.3 Deploying BIRT POJO Runtime with Spring
- 4.4 Deploying BIRT POJO Runtime with JBoss SEAM
- 4.5 Advanced Deployment Topics
- 4.6 Connection Profiles
- 4.7 Font Config
- 4.8 JDBC Drivers
- 4.9 Custom Extension Point Implementations
BIRT POJO Runtime Overview
To simplify application deployment, BIRT 3.7 features a new POJO based runtime. The new Runtime consists of a set of jars that can simply be added to the classpath of your application. While this affects the Runtime of BIRT the designer will continue to use the same OSGi based approach as previous versions of BIRT. The new Runtime is available for download on the BIRT web site. The download contains three packages that can be used depending on your deployment scenario.
BIRT POJO Viewer WAR
BIRT Viewer POJO Viewer Exploded WAR
BIRT POJO Engine
The Runtime also contains a ReportEngine directory. This directory contains all the jars needed to deploy either the Report Engine, the Design Engine or the Chart Engine. Use this package if you are writting a POJO application or writing your own custom web application.
Migration of Older Applications
Please see Birt_3.7_Migration_Guide for details on migrating applications to the new runtime. The migration guide covers deploying the Viewer to different application servers, API changes, and architecture differences.
BIRT POJO Viewer Deployment
The Viewer can be deployed as a standard Java EE based web application. Specific instruction are provided below.
Deploying BIRT POJO Runtime in a Servlet
Deploying BIRT POJO Runtime in a POJO
Deploying BIRT POJO Runtime with Spring
Deploying BIRT POJO Runtime with JBoss SEAM
Advanced Deployment Topics
If your reports use connection profiles supplied by the Data Tools Platform project (DTP), you will need to add a system or environment property that specifies a DTP workspace location. The genReport bat or shell script files show an example of setting this variable. If you are deploying these reports to the BIRT Viewer you will need to add the system property or set the environment variable in your application server. More details on this variable are available in the New and Noteworthy for DTP version 1.9
If you are modifying your font locations using the fontsConfig.xml files located in the org.eclipse.birt.report.engine.fonts_version plugin see this bug.
Adding a JDBC driver to the BIRT designer has not changed, but in the new runtime the driver jar(s) can
Custom Extension Point Implementations
If you have developed plugins that implement BIRT extension points these should continue to work if you add them to the classpath. For example, if you have developed an ODA data source extension to access data, or if you have developed an emitter simply add the jar for the exported plugin to your application classpath. If you are using the viewer, just copy your exported plugin to the viewer/WEB-INF/lib directory.