Deployment for multiple Repositories

Multiple Repositories can be required to provide support for more than one data center, for different geographical regions, and for running multiple customers.

Db2 only: It is recommended that not more than 50 repositories be defined in a Db2 subsystem that is referenced by each Analyzer. This is to prevent overload to the Analyzer and also for easier management of repositories.

You can locate multiple Repositories in one central location, or you can locate them in geographically dispersed locations. Multiple Repositories may be organized as follows:
  1. For a central location
  2. For geographically dispersed locations

Central location

Each Repository contains data that is divided up into logical units, for example:
  • Data center
  • Outsourced customer
  • Sysplex
Each Repository has its own database. For Db2®, all repositories must reside in the same Db2® subsystem. For SQLite, each repository must reside in its own SQLite database. For Db2® only, the advantage of this configuration is that reporting can be performed on data across all repositories. With this configuration, all repositories can share the same Global Knowledge Base (GKB) and you only have to maintain a single copy of the GKB.

Geographically dispersed locations

Each Repository is defined with its own database at a specific geographic site as a stand alone operation. Reporting can only be performed for each specific Repository. The disadvantage with this configuration is that it can be necessary to consolidate Repository data to a central site for reporting purposes.