Bookshelf Home | Contents | Index | Search | PDF

Upgrade Guide for Microsoft Windows > Preupgrade Tasks >

Preparing Development Environment Repositories

---

Four separate repositories are used during the development upgrade process:

• Your existing development repository. To prevent a naming conflict, before you run the upgrade, rename your existing development repository (Siebel Repository) to Prior Customer Repository. After the upgrade, your new Release 7.5 development repository is given the name Siebel Repository.

  NOTE:  When you rename the repository, you may prefix the name with additional characters (except for a leading space). Do not append the repository name with additional characters, because this results in an error.

• Three new repositories. These are automatically loaded when you run the upgrade wizard:
  • Prior standard repository (Release 6.x or 7.x)
  • New standard repository (Release 7.5)
  • New customer repository (Release 7.5), which after the merge becomes the customized 7.5 repository.

Verify Repository Names

Before these new repositories are loaded, verify that your existing repositories do not use the names reserved for the upgrade process:

• New Customer Repository. Your new custom repository, that results from the merge and includes your custom configurations.
• New Siebel Repository. The new Siebel standard repository.
• Prior v6.x Siebel Repository (for upgrades from Release 6.x).
• Prior v7.x Siebel Repository (for upgrades from Release 7.x).

Checking In Archived Release 6.x Repository Objects

If you archived Release 6.x repository objects as .sif files that you want to have available in your Release 7.5 application, you must check these objects back into the repository before you begin your upgrade. If you do not check these objects back into the repository, they will not be upgraded.

NOTE:  You only need to check in those archived objects that you need in the future and want to have available in your upgraded application.

Renaming Your Existing Development Repository

Use the version of Siebel Tools that matches your old version of Siebel eBusiness Applications (for example, Siebel Tools Release 6.x for upgrades from Release 6.x). Connect directly to the development database server, and then perform the following steps to make sure that your existing repositories follow the correct naming conventions.

To rename the repository

1. Using the appropriate prior version of Siebel Tools, connect to the Siebel Database Server.
2. Change the name of the existing repository, as described below:
   1. In the Object Explorer, click the Types tab.
   2. Click Repository.
   3. In the Repository view, click Name.
   4. Locate the appropriate repository in the list applet and rename it Prior Customer Repository.
3. Step off the list to commit the record to the database.

   The upgrade process verifies the repository names.

   • If no repository is named Prior Customer Repository, the Siebel Repository is renamed to Prior Customer Repository in the target database so that the upgrade executes properly.
   • If the validation check fails, verify that the repository name is not prefixed with a leading space.

NOTE:  When you rename the repository, you may prefix the name with additional characters (except for a leading space, which causes the validation to fail).
Do not append the repository name with additional characters, because this results in an error.

For more information about renaming repositories, refer to Siebel Tools Reference.

Bookshelf Home | Contents | Index | Search | PDF