Using Siebel Tools > Managing Repositories >

Guidelines for Naming Repositories

You must establish and maintain a naming convention for all repositories in their respective environments. There are several dependencies on repository names—for example, Siebel servers 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:

• Use the default name, Siebel Repository, whenever possible. Change this only if you have a compelling reason, because the default configuration of Siebel eBusiness Applications and Siebel documentation assume this name is being used.
• Use the same repository name for the active repository in your test environment and for the current working repository in your production environment. 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 perform the migration process.
• 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.5.3 Original for the initial repository shipped with Siebel eBusiness Applications version 7.5.3.