1. Database Upgrade Guide
  2. Development Environment

Development Environment

This environment is where developers customize Siebel Business Applications. The development environment is also known as the "design repository" or "DR" environment, and is the only environment in which repository objects can be updated.

A development environment includes the following Siebel CRM modules:

  • Siebel Gateway
  • Siebel Server, hosting Web Tools and one or more Siebel Business Applications
  • Siebel Database Server files installed on a Siebel Server
  • RDBMS server and Siebel database
  • Siebel Application Interface
  • Siebel Tools installed on workstations running a supported Windows environment.

Upgrading the development environment involves these tasks:

  1. Prepare application data. These tasks prepare test data for migration.
  2. Upgrade Repository (UpgRep). You run the Database Configuration Wizard in upgrep mode. They perform a basic upgrade of the Siebel database schema and load repositories to prepare for the repository merge.
  3. Merge repository. You merge your existing repository with the repository from the new Siebel CRM release. Postmerge utilities upgrade form applets and verify that applets and views are configured correctly.
  4. Run postmerge utilities. You run a set of utilities that examine the merged repository. The utilities analyze your customizations and apply changes to them as needed to conform to the user interface in the new release.
  5. Upgrade Physical Database (UpgPhys). You run the Database Configuration Utilities in upgphys mode. They further upgrade the Siebel database with changes resulting from the repository merge and they complete the database upgrade.

    The Database Configuration Utilities also generate the customer repository definition file and logical schema definition file that are used as input to the test environment and production upgrades.

    Note: During the sync process, custom columns in the Siebel schema that aren't in the Siebel Repository aren't deleted, but custom indexes in the Siebel schema that aren't in the Siebel Repository are deleted.