Use of multiple user databases

If some developers on your team work on multiple projects, you can store the schemas for the HCL Compass user databases that are linked to those projects in one schema repository, as shown in the following figure.
Figure 1. One schema repository for multiple HCL Compass user databases

One schema repository has two schemas, Schema 1 and Schema 2. Project VOB PVOB1 is linked to HCL Compass user database 1 which uses Schema 1 in the repository. Project VOB PVOB2 is linked to HCL Compasst user database labelled 2 which uses Schema 2 in the same repository.

The databases that are named Compass User Database 1 and Compass User Database 2 are linked to the same schema repository.

If you use multiple user databases, give each one a unique name. If a developer tries to access a user database whose name is not unique, the authentication can fail. In using the command line interface to be authenticated, a developer can specify only the name of the user database. (The graphic user interface requires that the database set (connection) be supplied.) If multiple user databases share the same name, the software cannot distinguish the difference in databases that have the same name.

Using a single schema repository allows developers to switch between projects easily. If you store the schemas in different schema repositories, developers must connect to each schema repository once when they switch projects. The user name and password are stored locally for each connection that they use. The project manager or developer can provide or update the credentials by using the crmregister command.