Using Siebel Tools > Managing Repositories > Viewing, Renaming, Comparing, and Configuring Repositories >

Renaming Repositories

It is recommended that you use Siebel Repository as the name of the repository that you use in your production environment. If you want to rename the repository, then it is recommended that you use the procedure that this topic describes.

To rename repositories

1. Make sure all developers check in all projects that are currently checked out from the repository that you want to rename.

   For more information, see Checking Out and Checking In Projects and Objects.

2. Log in to Siebel Tools, connected to the server database.
3. Display the Repository object type.

   For more information, see Displaying Object Types in the Object Explorer.

4. In the Object Explorer, click Repository.
5. In the Repositories list, locate the repository that you want to rename.

   For more information, see Locating and Modifying Object Definitions in the Object List Editor.

6. Enter the new name in the Name property, and then step off the record to save your modifications.

   For more information, see Guidelines for Naming Repositories.

7. Compile your modifications.

   For more information, see Compiling Your Modifications.

8. Communicate the name of the new repository to your developers and request that each developer get all projects from the server repository.

   For more information, see Getting All Projects from the Server Repository.

9. Modify the value of the Siebel Repository enterprise parameter to the new name of the repository.

   For information about how to modify an enterprise parameter, see Siebel System Administration Guide.

10. Modify the Application Main Repository Name parameter in the Object Manager.

Guidelines for Naming Repositories

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 that 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 that you use 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 Repositories.
• If your development environment uses multiple repositories, then use a unique and descriptive name for each repository. For example, you might use Siebel v8.2 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 from a prior custom configuration.