Using Siebel Tools > Managing Repositories > Renaming a Repository >

Guidelines for Naming a Repository

If you name a repository, then it is recommended that you use the following guidelines:

• Use a naming convention for all repositories that your Siebel CRM implementation uses. Siebel Servers reference a repository by name. The procedure you use to upgrade to a new version of Siebel CRM depends on the repository name. A consistent naming convention promotes successful configuration and testing and minimizes the work required to migrate a new repository or to do an upgrade.
• Use the default Siebel Repository name, where possible. You can modify this name only if it is absolutely necessary. The default configuration that Siebel CRM uses assumes that the repository name is Siebel Repository.
• Use the same repository name in your test environment and in your production environment. Using the same name simplifies the process of migrating a repository from development to test and from test to production. It also eliminates the need for you to modify the client configuration or server configuration during a migration. For more information, see Process of Migrating a Repository.
• If your development environment uses multiple repositories, then use a unique and descriptive name for each repository. For example, you might use Siebel v8.0 Original as the name of the repository when you install Siebel CRM. You can use another descriptive name for the repository that you use during an upgrade and for a repository that exists from a prior custom configuration.