Siebel Database Upgrade Guide for DB2 UDB 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 environments:

  • Development environment
  • Production test environment
  • Production environment

Development Environment

The development environment is where developers use Siebel Tools to customize Siebel 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 machine 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.

There are two scenarios for development environment upgrades:

  • Development environment database with DB2 UDB. If your development environment database is DB2 UDB, you must use the Siebel Database Upgrade Guide for your development environment upgrade. Then use this guide for your production environment upgrade.
  • Development environment database with DB2 UDB for z/OS. During DB2 for z/OS upgrades, the Siebel Upgrade Wizard generates the schema and output files. Your database administrator must review these files and apply them on the z/OS host.

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, 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 machine 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 Enterprises 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 Packager. This application creates installation packages for use by Siebel Mobile or Developer Web Client. For information about Siebel Packager, see Going Live with Siebel Business Applications.
  • Siebel Anywhere. This application builds distribution kits for remote users. For information about Siebel Anywhere, see Siebel Anywhere Administration Guide.

Mapping Your Environments

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

Table 4. Mapping Your Environments to Siebel Upgrade Processes
Environment Description
Recommended Upgrade

The environment has the following characteristics:

  • It is used primarily for development with Siebel Tools.
  • The Siebel database is a subset of your production database.
  • The environment is not used for technical support or training. Developers are usually installed as Mobile Web Clients.

Development environment upgrade.

The environment has the following characteristics:

  • It is intended for testing customizations before deploying them.
  • It is where you tune your upgrade SQL files to minimize production upgrade time.
  • There may be multiple upstream environments in addition to the production test environment. For example, these could include environments used by a product management group, Technical Support, and Quality Assurance.

Production test environment upgrade.

The environment is used for live business transactions by both local and remote users.

Production environment upgrade.

Siebel Database Upgrade Guide for DB2 UDB for z/OS Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices.