BIRT iHub stores metadata containing system, cluster, and volume configuration information in a database. In the default installation, BIRT iHub uses the open-source, PostgreSQL RDBMS. iHub also supports using other RDBMS, such as Oracle or a pre-existing PostgreSQL instance.
After installation of the default system, the system administrator uses System Console to switch to an alternative RDBMS. The database administrator must pre-configure the database by running SQL Data Definition Language (DDL) to install the iHub database and the cluster and volume schemas.
The database that contains BIRT iHub system, cluster, and volume metadata is a critical component of BIRT iHub System. To guard against data loss, the database administrator must back up the schema using the tools and resources of the third-party RDBMS.
For information about the recommended procedures to back up BIRT iHub cluster and volume schemas, refer to BIRT iHub System Administration Guide.
Support for the metadata database
If you encounter a problem with the operation of the metadata database, Actuate will work with you to resolve it. For example, Actuate may take any or all of the following actions:
Propose a change in your environment that avoids the problem.
Make a change in Actuate’s code to work around the problem.
In the case of PostgreSQL, engage with the development community to obtain a patch.
In the case of Oracle, help you to isolate the problem and report it to the vendor.
Downloading the installation packages
Download BIRT iHub from an Actuate download site using the URLs provided by e-mail.
Propose a change in your environment that avoids the problem.