|
Siebel Database Upgrade Guide > How to Perform a Siebel Database Upgrade >
Process of Upgrading a Siebel Development Environment
Upgrades from: All Siebel releases. Environments: Development environment only. Platforms: Windows and UNIX only. This topic does not apply to IBM z/OS. This process is part of a road map. See Road Map for Performing a Siebel Database Upgrade. This topic lists the steps required to upgrade a Siebel development environment to the current release. Print this topic and use it as a checklist for doing the upgrade. The topic is divided into sections, each containing a list of numbered steps. Complete each section in the order shown. Steps that apply only to upgrades from Siebel 6.x are marked as follows: 6.x upgrades only. CAUTION: Do not use this topic to perform a development environment upgrade on IBM z/OS. Instead, refer to Siebel Database Upgrade Guide for DB2 UDB for z/OS.
Check SupportWeb
- Check Siebel SupportWeb for recently published Technical Notes and Alerts regarding upgrade:
- SupportWeb > Installation and Upgrade
- SupportWeb > Technical Notes > Installation; Upgrade; Configuration-Dev Env; Configuration-General
- SupportWeb > Siebel Alerts > Installation; Upgrade; Configuration Dev Env; Configuration-General
- About Siebel Upgrade Planning Resources
Upgrade the Servers
Verify you have identified all the maintenance releases, Fix Packs, and quick-fix patches required for the upgrade. These requirements are located on Siebel SupportWeb under Product Documentation > Maintenance Release Guides. CAUTION: Do not install a new Siebel database as part of upgrading the Siebel Enterprise.
To perform the following steps, see the Siebel Installation Guide for the operating system you are using.
- Upgrade the Gateway Name Server, Siebel Servers, and Siebel Web Server Extension (SWSE).
For information upgrading these Siebel Enterprise components, see Siebel Installation Guide for the operating system you are using.
- Install the Siebel Database Server files on the Siebel Server you will use to perform the upgrade. You only need to install the database server files for the database type that you are upgrading.
- Install language packs for your currently deployed languages and any new languages.
- If you have customized the configuration of Enterprise components, such as Siebel Servers, you must manually enter the customizations in the upgraded environment. See Going Live with Siebel Business Applications.
Upgrade Third-Party Software
- Upgrade third-party software as required due to dependencies on Oracle's Siebel software or other installed software. For example, you may need to upgrade the following software:
- Actuate Server (Siebel Reports Server).
- Operating system software. Some database upgrades require newer versions of AIX or Windows.
Upgrade the RDBMS
- If required, upgrade the RDBMS version. Refer to the vendor's documentation to perform the upgrade:
Pre-Upgrade Tasks for the Siebel Database
These steps apply to all database types.
- Review guidelines for configuring the RDBMS. See the Siebel Installation Guide for the operating system you are using.
- Verify that the Workflow Monitor and Workflow action agents have processed all pending requests.
- Stop the Siebel Servers and the Siebel Gateway Name Server.
- Perform the tasks in Basic Database Preparations for a Siebel Upgrade.
Pre-Upgrade Tasks for IBM DB2
- Perform the tasks in Preparing an IBM DB2 Database for a Siebel Upgrade.
- Execute runstats on the Siebel database. This will improve upgrade performance.
Pre-Upgrade Tasks for Oracle
- Perform the tasks in Preparing an Oracle Database for a Siebel Upgrade.
- Run the Oracle Analyze command on the Siebel database. Highly fragmented indexes can cause the upgrade to fail.
Pre-Upgrade Tasks for MS SQL Server
- Perform the tasks in Preparing an Microsoft SQL Server Database for a Siebel Upgrade.
- Run Microsoft SQL Server statistics. This will improve upgrade performance.
Pre-Upgrade Tasks for Application Data
- Perform the tasks in Technical Note 521 on Siebel SupportWeb. Table 17 shows the applicability of the tasks in the Technical Note.
Table 17. Tasks in Technical Note 521
|
|
Location and amendment of S_VIEW_WTMPL_IT.ITEM_NUM records |
Development, production test, production |
Update multi-value group (MVG) and association list applets |
Development only |
Update unnamed controls in applet web template items |
Development only |
- Perform the tasks in the Technical Notes and Alerts on Siebel SupportWeb shown in Table 18.
Table 18. Tasks in Technical Notes and Alerts
|
|
Technical Note 481 |
Development only |
Alert 1113 |
Development only |
Technical Note 580 |
Development only |
- Perform the tasks in Preparing Siebel Application Data for Upgrade.
Preparing Developers for the Upgrade
- Back up the development database.
- Verify that all developers have checked in their projects and that all projects are unlocked.
- Verify that all developers have disconnected from the database. The only open account must be the account that is performing the upgrade.
- Install the new Siebel Tools and license keys on development workstations.
NOTE: Keep at least one copy of the previous version of Siebel Tools. You will need it to perform repository operations before the repository merge.
Perform all remaining tasks with the new Siebel Tools, unless stated otherwise.
Upgrade Siebel Database Schema (upgrep)
- Renaming the Siebel Repository.
- (Optional) Changing the Siebel Database Server Configuration Utilities Language.
- Run the Database Configuration Wizard:
- Edit generated SQL files as required by Siebel Technical Notes, Alerts, Release Notes or other publications. For a complete list, see the Installation and Upgrade Portal page on Siebel SupportWeb.
- Resume the upgrade: Starting the Siebel Upgrade Wizard.
- Review the upgrade logs and resolve errors:
- If the upgrade contains unacceptable errors, do the following:
- Restore the backup of the database.
- Correct the errors.
- If errors occurred because you entered incorrect information in the Database Configuration Wizard, see Regenerating SQL Files for a Siebel Upgrade.
- Rerun the Database Configuration Wizard.
- Multilingual deployments: Perform the steps in Technical Note 447 on Oracle's Siebel SupportWeb to import language-specific repository strings and seed data into the upgrade repositories.
- Back up the upgraded database.
Prepare for Repository Merge
- 6.x upgrades only: Running the Siebel Repository Preparation Wizard.
- 6.x upgrades only: If the Repository Preparation Wizard log files contain unacceptable errors, do the following:
- Restore the backup of the upgraded database.
- Correct the errors.
- Rerun the Repository Preparation Wizard.
- Set the Upgrade Ancestor property for copied objects. See Configuring Siebel Repository Objects to Inherit Upgrade Behavior.
- See Configuring Siebel Tools for the Repository Merge.
- (IBM DB2 and Microsoft SQL Only) Run database statistics on the Siebel database. If upgrading from Siebel 7.0.x or 7.5.x, run statistics specifically on S_SYM_STR and S_SYM_STR_INTL.
Running statistics on the Siebel database improves merge performance.
Perform Repository Merge
Use the upgraded version of Siebel Tools to perform these tasks.
- Performing a Siebel Repository Merge.
- Reviewing the Siebel Repository Merge Log Files.
- If the repository merge contains unacceptable errors, do the following:
- Restore the backup of the upgraded database.
- Correct the errors.
- Rerun the repository merge.
- Generating Siebel EIM Temporary Columns.
- Reset Siebel Tools configuration. See Configuring Siebel Tools for the Repository Merge.
- Back up the Siebel database.
Upgrade Custom Database Schema (upgphys)
- Run the Database Configuration Wizard:
- Run the Upgrade Wizard: Starting the Siebel Upgrade Wizard.
- Review the upgrade log files and resolve errors:
- If the upgrade contains unacceptable errors, do the following:
- Restore the backup of the database you made after the repository merge.
- Correct the errors.
- Repeat the steps beginning after the backup.
- Manually Archiving Siebel Upgrade Log Files.
- Back up the upgraded database.
Initialize and Extract Developers' Local Databases
- Install the new release of Siebel Tools on developers' machines.
- Initialize and extract the local database on development machines. For more information, see Developing and Deploying Siebel Business Applications.
Migrate Created or Modified Applets and Views
6.x upgrades only: The steps in Migrate Created or Modified Applets and Views apply only to upgrades from Siebel 6.x.
- (Optional) Identifying What Will Be Migrated in a Siebel 6.x Upgrade.
- Exposing Hidden Properties of Siebel Applets and Views.
- Running the Siebel Web Client Migration Wizard.
- Reviewing Siebel Applet and View Migration
- Remigrate applets and views as needed. See Remigrating Siebel Applets and Views.
- Regenerating the Siebel Postmerge Utilities Log.
Review the User Interface
- Reviewing Siebel Repository Object Property Conflicts
- Review the following topics on UI upgrade before proceeding:
- If you performed an ICL upgrade and chose Label on Top, revise the cascading style sheet. See Setting Label Alignment for Siebel Text Fields.
- Create a new SRF file to assist in UI testing. For information on creating an SRF file, see Developing and Deploying Siebel Business Applications.
- If you customized style sheet or Web template files in the previous release, reimplement those customizations in the new release as desired.
Carefully review the UI in the new release before reimplementing customizations to these files.
- Perform the tasks in Reviewing the Siebel User Interface.
- The postmerge utilities do not convert certain types of flow-based applets to grid-based applets. For example, they do not convert custom form applets to grid-based applets. See the "Editing Applet Layout" portion of Configuring Siebel Business Applications and convert remaining flow-based applets as desired.
Postmerge Development Tasks
- 6.x upgrades only: Perform the tasks in Postmerge Development Tasks for Siebel 6.x Upgrades.
- Perform the tasks in Siebel Postmerge Development Tasks.
- Resolve any business component and join conflicts.
- Deleting Unneeded Siebel Repository Files.
Postupgrade Tasks for Database and File System
- Perform the tasks in Postupgrade Tasks for the Siebel Database and File System.
- Reset upgrade-specific database and database server parameters back to their recommended settings for production. See Siebel Installation Guide for the operating system you are using for recommended parameter settings.
- If you exported data from interface tables before the upgrade, review the database and import the data as desired. See Siebel Enterprise Integration Manager Administration Guide.
- Upgrade Planning for Siebel RC2 or AES Encryption.
- Generate a Siebel Remote database template file. See Siebel Remote and Replication Manager Administration Guide.
- (Oracle database 9i and later). Set Optimizer Mode to CBO. See Setting Oracle Database Configuration Parameters for a Siebel Upgrade.
- Run database statistics.
NOTE: The upgrade is complete. The remaining topics deal with configuration and validation tasks.
Postupgrade Tasks for Applications Configuration
- Installing New Siebel License Keys During an Upgrade.
- If applicable, review the results of the Person and Organization merge. Make configuration changes as required. To determine applicability or obtain more information, see About the Siebel Party Model.
- Perform the tasks in Postupgrade Tasks for Siebel Applications.
- Verify the function of interfaces in integrated applications.
- Activate and deploy workflows.
- If you have set up integrations for transferring data to or from third-party applications using Siebel EAI, verify the integrations are configured correctly. For information on EAI, see Overview: Siebel eBusiness Application Integration Volume I.
- If you have used EIM to set up batch processing jobs, verify EIM is configured correctly. For information on EIM, see Siebel Enterprise Integration Manager Administration Guide.
System Tests
- Use available test data to perform unit testing. Validate the operation of the application in the following areas:
- User interface
- Data interfaces
- Integrity of migrated data
- Workflow function
Prepare for Transition to Production Test Environment
- Create a new SRF file. For information on creating an SRF file, see Developing and Deploying Siebel Business Applications.
- If you revised the repository after running upgphys, you must regenerate the repository definition files. See Regenerating the Siebel Repository Definition Files.
|
