Using a third-party RDBMS with an Encyclopedia volume
Actuate automatically installs the iHub system and Encyclopedia volume schemas in the OOTB PostgreSQL RDBMS installation. Installing the schemas in a pre-existing PostgreSQL RDBMS or alternative RDBMS, such as DB2, Oracle, or SQL Server, requires manually running a SQL script containing the appropriate Data Definition Language (DDL) statements. The installation sections of this book contain chapters that provide detailed, step-by-step descriptions on how to perform these operations.
Actuate BIRT iHub only supports installing the metadata for Encyclopedia volumes in the same schema, not separate schemas or separate databases. In Oracle, there is a one-to-one relationship between a database user and a schema. A schema is not a separate entity. An Actuate DB2, PostgreSQL, or SQL Server installation requires this one-to-one relationship between a database user and a schema for consistency.
In a pre-existing RDBMS installation, the database administrator first creates a schema owner and a database user by running a SQL DDL script. During iHub installation, the iHub system administrator provides the schema owner and database user credentials. The iHub installation program connects to the RDBMS, creates the necessary Encyclopedia volume database structures, then loads the metadata. The iHub system interacts with the third-party RDBMS using these database user credentials.
Only the metadata that specifies the Encyclopedia volume configuration are in the database. Designs, documents, information objects, and other iHub data objects are stored in the file system.