1. Database Upgrade Guide
  2. Development Environment

Development Environment

This environment is where developers use Siebel Tools to customize Siebel Business Applications, and where customizations are made to the Siebel Runtime Repository. When your Siebel Business Applications instance goes live in a production environment, the Runtime Repository is where all object definitions are retrieved, then displayed to users in your Siebel CRM user interface.

A development environment includes the following Siebel CRM modules:

  • Siebel Gateway

  • Siebel Server

  • 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. This includes the local database running on developers’ Siebel Mobile Web Clients.

  • Siebel Business Applications and test data required to verify the basic function of Siebel Runtime Repository.

Upgrading the development environment involves these tasks:

  1. Prepare application data. These tasks prepare test data for migration.

  2. Upgrade database (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. Both upgrep and upgphys modes are run as a single step in the Database Configuration Utility.

  3. Merge repository. You use Siebel Tools to merge your existing repository with the repository in the new release. Postmerge utilities upgrade form applets and verify that applets and views are configured correctly.

  4. Run postmerge utilities. You use Siebel Tools to 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 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 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 synchronization process, custom columns in the Siebel schema that are not in the Siebel Repository are not deleted but custom indexes in the Siebel schema that are not in the Siebel Repository are deleted.