Other Considerations

Object Repository

A critical first step in configuring Hubble is to create an Object Repository. The below excerpt from the Hubble Administration and Configuration Guide explains the purpose, the requirements, and the fundamental components of the Object Repository.

The Object Repository can reside on any relational database server and is not restricted to an Oracle database.

The Object Repository contains the application’s configuration information, user-specific information, and objects such as hierarchies, calculations and Reusable Inquiry Objects. Report parameters are stored in the repository, but not the report results themselves.

The repository needs to be created on a relational database server that is available whenever the user logs on to the Hubble application. The application uses the Repository to perform critical processes such as user verification and validation of permissions. The application has a built-in database layer that will allow access from the application to the database.

The repository contains a number of tables that are created during the initial application configuration. These tables can be created in an existing database/schema/library, but it is preferable for disaster recovery purposes to create a separate database/schema/library to hold the new repository tables. All users need to have read/write permissions to the Repository; this is typically handled using a system user profile.

The size of the Repository differs from site to site depending on the number of users and reports created and saved. The majority of customers have repository databases under 1GB in size and they should not require any special configuration with regards to portioning, etc.

Performance

Depending on how your database has been tuned, there is the potential to affect the performance of your system. Typically the effect should be same as running a SQL query on your database, which should be negligible.

Maintenance

Table Permissions

DBAs should note that revoking table permissions on the Hubble user after an installation will cause problems on the front-end tool, and would likely stop the related reports from working correctly.

Environment Refresh

Refreshing the environment containing the Hubble schema from another which does not contain it will require re-installation of the schema. This would likely only be an issue where the install does not exist on the production environment.

Database Passwords

If the Hubble database user password is changed, a corresponding change will need to be made in the Administrator application. A new RepositorySelection.xml file will need to be generated and distributed to users’ client machines if the password change is on the repository connection.