Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "BIRT 3.7 Runtime Deployment Guide"
(New page: {{Backlink|BIRT/FAQ/Deployment}} __TOC__ ==Overview== With the release of BIRT 3.7, BIRT now provides a POJO Based Runtime. This page will cover different scenarios for deploying the ne...) |
|||
| Line 3: | Line 3: | ||
__TOC__ | __TOC__ | ||
| − | ==Overview== | + | ==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 and is structured as illustrated in the following diagram.<br> | |
| + | |||
| + | [[Image:BIRTPOJOruntime.png]] | ||
==Migration of Older Applications== | ==Migration of Older Applications== | ||
Revision as of 16:21, 21 June 2011
< To: BIRT/FAQ/Deployment
Contents
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 and is structured as illustrated in the following diagram.
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.
Deploying BIRT POJO Runtime with Spring
TBD
Deploying BIRT POJO Runtime with JBoss SEAM
TBD