Bookshelf v7.5: Naming Repositories

Configuration Guidelines > Managing Repositories >

Naming Repositories

You must establish and maintain a naming convention for all your repositories in their respective environments. Several things depend on repository names—for example, both the Siebel eBusiness Applications client and application server programs point to a specific repository by name. Also, the procedures for upgrading to new versions of Siebel eBusiness Applications depend on repository names.

A consistent naming convention promotes successful configuration and testing while it minimizes the work required to migrate new repositories or perform upgrades. Follow these guidelines when determining the naming conventions for your repositories:

Decide on a repository name for your production environment. By default, it is Siebel Repository. Change this only if you have a compelling reason, because much of the Siebel documentation and the default configuration of the Siebel eBusiness Applications assume this name is being used.

Choose the same name for the active repository in your test environment and for the current working repository in your production environment. The default name is Siebel Repository. Using the same name simplifies the process of migrating repositories from development to test and from test to production. It also eliminates the need to change your client or application server configurations when you do so.

Use descriptive names for the other repositories in your development environment. Typically, your development environment has a number of repositories in addition to the current repository that is being configured. These may include the initial repository loaded with your Siebel application, other repository versions used in Siebel application upgrades, and repositories from previous versions of your custom configuration. Give these repositories unique and fully descriptive names — for example, Siebel v7.0 Original for the initial repository shipped with Siebel eBusiness Applications version 7.0. For more information, see Performance Guidelines.