Siebel Database Upgrade Guide for DB2 for z/OS > How the Siebel Database Upgrade Works >

About Siebel Upgrade Environments

Upgrades: All upgrades.

Environments: All environments.

This guide describes how to upgrade three database environments:

• Development environment
• Production test environment
• Production environment

Detailed information on each database environment is provided in the remainder of this topic. For an overview of the steps involved in upgrading each database environment, see the chapter in Siebel Database Upgrade Guide that provides an overview of the upgrade process.

Development Environment

The development environment is where developers use Siebel Tools to customize Siebel Business Applications. The development environment upgrade merges these customizations with the new Siebel release. The merged repository and schema definitions become inputs to the production upgrade.

A development environment contains the following elements:

• Siebel Server
• Web server and Siebel Web Server Extension
• Siebel Gateway Name Server
• Siebel Database Configuration Utilities installed on the same computer as the Siebel Server
• RDBMS server and Siebel database
• Siebel Tools installed on workstations running a supported Windows environment. This includes the local database running on developers' Mobile Web Clients.
• Siebel applications and test data required to verify the basic function of newly compiled SRF files.

Production Test Environment

The production test environment is where you test the upgraded release to validate its function and performance before deploying it to users. This is also where you tune the upgrade process to minimize the time required to perform your production upgrade.

By tuning the production upgrade scripts in a test environment, you can significantly reduce the time required to complete the production upgrade. For this reason, the production test environment database must contain the same data volume and topography as your production database.

This environment includes the following elements:

• Siebel Enterprise Server, including at least one Siebel Server and an RDBMS server and Siebel database
• Web server with a Siebel Web Server Extension installed
• Siebel Gateway Name Server
• Siebel Database Configuration Utilities installed on the same computer as the Siebel Server
• All the Siebel applications currently installed in your production environment
• A copy of the Siebel database installed in your production environment

You perform the following processes in the production test environment:

• Test the upgraded release to validate its function and performance before deploying it to users.
• Tune the upgrade process to minimize the time required to perform your production upgrade.

Tuning the upgrade scripts can significantly reduce the time required to complete the production upgrade.

Production Environment

The production environment is your live business environment, where your internal and external users interact with applications and generate actual business data. The production environment includes all your Siebel Enterprise Servers worldwide.

The upgrade process assumes all production environment databases are completely separate from the development environment and production test environment databases.

Oracle provides these tools to help you transition from production test to production:

• Siebel Application Deployment Manager (ADM). This application migrates administrative data such as lists of values (LOVs) from the production test environment to the production environment. For further information about ADM, see Siebel Application Deployment Manager Guide.
• Siebel Anywhere. This application builds distribution kits for remote users. For information about Siebel Anywhere, see Siebel Anywhere Administration Guide.

Mapping Your Environments

You might have more or fewer environments than those described above. Table 4 gives recommendations for mapping your environments to the ones described in this guide.