Designing BIRT Information Objects
Designing BIRT Information Objects provides information about using Information Object Designer to create information objects and publish them to an Actuate BIRT iServer Encyclopedia volume. This manual also describes how to configure a database type for use with Information Object Designer.
Designing BIRT Information Objects includes the following sections:
*
Creating information objects using Information Object Designer. This part explains how to create information objects using Information Object Designer.
*
Introducing Information Object Designer. This section defines the term information object and describes the Information Object Designer user interface.
*
Creating projects, data connection definitions, and maps. This section describes how to create a project, data connection definitions, and maps prior to creating information objects.
*
Creating information objects. This section describes how to create information objects.
*
Caching information objects. This section describes how to cache information objects to improve performance and reduce the load on production databases.
*
Building and publishing a project. This section describes how to build and publish an Actuate BIRT project to an Encyclopedia volume.
*
Assessing the impact of project changes. This section describes how to assess the impact of a change to a file, column, or parameter on other files in an Actuate BIRT project.
*
Actuate SQL reference. This section describes the differences between Actuate SQL and ANSI SQL-92.
*
Configuring database types. This part explains how to configure a database type for use with Information Object Designer.
*
Understanding database types. This section defines the term database type, describes the preconfigured database types, and gives an overview of database type configuration.
*
Configuring connection types. This section gives the requirements for JDBC drivers and describes how to configure a connection type.
*
Mapping data types. This section explains how database data types are mapped to Actuate SQL data types at design time.
*
Mapping functions and operators. This section explains how to map Actuate SQL functions and operators to their database equivalents.
*
Mapping literals and clauses. This section explains how to map Actuate SQL string and timestamp literals and GROUP BY and ORDER BY clauses to their database equivalents.
*
Working with collations and byte-based strings. This section explains how to choose Integration service and database collations and how to work with a database that processes strings by byte.
 
 

Additional Links:

Copyright Actuate Corporation 2012