Jump to: navigation, search

Difference between revisions of "BIRT 3.7 Runtime Deployment Guide"

Line 30: Line 30:
===Deploying BIRT POJO Runtime with JBoss SEAM===
===Deploying BIRT POJO Runtime with JBoss SEAM===
Engine Deployment
deploying engine in servlets
deploying engine in pojos
deploying engine to JBoss SEAM
deploying engine to Spring

Revision as of 16:26, 21 June 2011

< To: BIRT/FAQ/Deployment

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.

BIRT POJO Viewer Deployment

The Viewer can be deployed as a standard Java EE based web application. Specific instruction are provided below.

BIRT POJO Viewer Websphere Deployment
BIRT POJO Viewer WebLogic Deployment
BIRT POJO Viewer JBOSS Deployment
BIRT POJO Viewer Tomcat Deployment

Engine Deployment

===Deploying BIRT POJO Runtime in a Servlet TBD ===Deploying BIRT POJO Runtime in a POJO TBD

Deploying BIRT POJO Runtime with Spring


Deploying BIRT POJO Runtime with JBoss SEAM