- Design Center
- Deployment Center
The BIRT Runtime contains three different packages: the Report Engine, the exploded Sample Viewer WAR, and the Sample Viewer WAR. Your choice of package will depend on your deployment scenario.
In this section you will find information on using these options.
This section provides an overview of the BIRT architecture, the BIRT components, the Eclipse components upon which BIRT relies, and the relationships that tie them all together. This guide includes the following topics:
This section provides an overview of the BIRT Report Object Model (ROM) and the primary elements that comprise the model. ROM defines the rules for constructing a valid report design. ROM, therefore, is the model for the BIRT report design, template, or library. This guide includes the following topics:
Beyond the BIRT Report Designer packages, BIRT provides a number of other separate packages as downloadable archive files on the Eclipse web site. Some of these packages are stand-alone modules, others require an existing Eclipse or BIRT environment, and still others provide additional functionality to report developers and application developers. This section describes the steps required to install the BIRT packages shown in the following list:
One way to view a BIRT design on the web is to deploy the BIRT Sample Viewer to an application server, such as Apache Tomcat, IBM WebSphere, JBoss, or BEA WebLogic. This section provides information about deploying the BIRT Sample viewer using the compressed or exploded WAR. This guide includes the following topics:
BIRT provides a comprehensive public API that developers can use to create custom BIRT based applications. The public API consists of the classes and interfaces in the following package hierarchies:
This section will give a general overview of these APIs. For more detail, see the BIRT Java Docs section below. Learn More
A BIRT based application uses the BIRT report engine API to generate BIRT output files from BIRT design (.rptdesign) files. Typically, the application produces the output as a formatted file or stream, in HTML or PDF format. Alternatively, the application creates an output document (.rptdocument) file that contains the report content in binary form and renders the output to one of the supported output formats later.
This section describes the fundamental requirements of a BIRT based application and describes the BIRT API classes and interfaces that you use in the application. This section also provides detailed information about the tasks that a BIRT based application performs. This section will cover many of the most important classes. For more detail, see the BIRT Java Docs section below. Learn More
This section describes the basic requirements of a charting application and demonstrates how to use the BIRT charting API to create a new chart and modify an existing chart definition. The BIRT chart engine provides the BIRT charting API. Classes and interfaces in this API support:
You'll also learn how to customize an existing chart and create a new chart within a BIRT application. This section will cover many of the most important classes. For more detail, see the BIRT Java Docs section below. Learn More
For more information about programming with the DEAPI, see the Design Center.
For more information about Java Docs, see the Design Center