BIRT iHub uses JDBC for connecting to the metadata database. The BIRT iHub run-time JRE environment supports Java 6.0 and 7.0. Any JDBC driver must be compatible with these JRE versions.
iHub requires a JDBC driver that complies with the JDBC 3.0 specification or later. The function Driver.jdbcCompliant( ) must return TRUE. DatabaseMetadata.getJDBCMajorVersion( ) must return 3 or greater than 3.
A system administrator, who decides to customize BIRT iHub to connect to a database other than the OOTB PostgreSQL database, must ensure that the JDBC driver returns adequate information about the types on the database. At a minimum, the database must return the common data types, such as integer, floating point, and character. If the database does not return these common data types, then the database administrator must customize the database mapping framework to specify the types.
The JDBC driver must also support the following features:
Scrollable cursor
Retention of a cursor after commit
Update using a prepared cursor
When using connection pooling, the tracing functionality of the JDBC driver captures connection pool run-time statistics.
About international character sets
BIRT iHub operates on the assumption that the metadata database is configured to run with UTF-8 encoding. Any other database encoding scheme requires configuring the connection parameters to specify the database encoding. The driver must handle the conversion to UCS2.
Administrative reports
The default iHub volume contains sample BIRT reports that provide information using the metadata and data extracted from the OOTB database, including job schedule, file, and user tracking and usage and error logging. Installing the sample volume is an option in a custom installation.
Supported operating systems
Actuate BIRT iHub supports the following operating systems:
Scrollable cursor