Upgrade Guide for DB2 UDB for z/OS > How to Perform the Upgrade >

Process of Upgrading a Development Environment from the Midtier

Upgrades: All upgrades.

Environments: Development (midtier-centric) environment.

This process is part of an upgrade roadmap. See Roadmap for Performing the Upgrade.

This topic lists the steps required to upgrade a development environment to the current release from the midtier. 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 Release 6.2.1 of Siebel Financial Services (FINS) are marked as such.

Upgrade Third-Party Software

1. Upgrade third-party software as required due to dependencies on 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.

     For further information, see Siebel System Requirements and Supported Platforms on Oracle Technology Network.

Upgrade the Servers

Verify you have identified all the maintenance releases, Fix Packs, and quick-fix patches required for the upgrade. These requirements are documented in Siebel Maintenance Release Guide on My Oracle Support.

To perform the following steps, see the Siebel Installation Guide for the operating system you are using and Implementing Siebel Business Applications on DB2 UDB for z/OS.

2. Install the Siebel Gateway Name Server, Siebel Servers, and Siebel Web Server Extension (SWSE).

   The upgraded Siebel Servers will not work correctly with the RDBMS server until after you have upgraded the Siebel Database to the new release.

3. Install the Siebel Database Server files on the Siebel Server you will use to perform the upgrade.
4. Install language packs for your currently deployed languages and any new languages.
5. 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.

NOTE:  You do not install a new Siebel database as part of upgrading the Siebel Enterprise.

Upgrade the RDBMS

6. If required, upgrade the RDBMS version. Refer to the vendor's documentation to perform the upgrade. For information on supported RDBMS systems, see Siebel System Requirements and Supported Platforms on Oracle Technology Network.

Identify and Resolve Duplicate Row IDs

7. 6.2.1 upgrades only: Identifying and Resolving Duplicate Row IDs.

   After you install the Siebel Database Server software, but before you upgrade to this release, you must identify and resolve any duplicate row IDs in your Siebel Database.

Preupgrade Tasks for the Siebel Database

8. Review Siebel Technical Notes and Siebel Alerts on upgrading to the current release. Make revisions to the upgrade process as required. See Important Upgrade Planning Resources.
9. Review 477519.1 (Article ID) on My Oracle Support. This document was previously published as Siebel Technical Note 521. It contains important changes to database records and repository objects that must be made during the upgrade. See Important Upgrade Planning Resources.
10. Review guidelines for configuring the RDBMS. See Implementing Siebel Business Applications on DB2 UDB for z/OS.
11. Verify all developers have checked in their projects.
12. Verify that the Workflow Monitor and Workflow action agents have processed all pending requests.
13. Stop the Siebel Server and the Siebel Gateway Name Server.
14. Verify there are no open database connections.
15. Perform the tasks in Basic Database Preparations.

Preupgrade Tasks for a Development Environment Upgrade

16. Perform the tasks in Preparing a Development Environment for Upgrade.

Preupgrade Tasks for Application Data

17. Perform the relevant tasks in Preparing Application Data for Upgrade.

    Some of these tasks are optional, depending on the currently installed Siebel products and your upgrade path. Review and perform these tasks as necessary.

Upgrade Siebel Database Schema (upgrep)

18. Install Siebel Tools on development workstations. Keep at least one copy of the previous version of Siebel Tools. You will need it to perform repository operations before the repository merge.
19. Migrating Repository Objects to the Standard UI.
20. Back up the development database. (If you backed up the database as part of an RDBMS upgrade, ignore this step.)
21. Run the Database Server Configuration utility on the midtier and enter development environment information to create the upgrade configuration file:
    • Preparing to Run the Database Server Configuration Utility.
    • Running the Database Server Configuration Utility Under Windows.
    • Running the Database Server Configuration Utility Under UNIX.

      When running the Database Server Configuration utility, choose the following settings:

    • Upgrade Options: Upgrade Siebel Database Schema (upgrep)
    • Environment Type: Development

      The master UCF file is updated with the development environment configuration.

22. Enter Yes to launch the Siebel Upgrade Wizard to start the database upgrade process. SQL commands are executed on the development environment database until the Upgrade Wizard stops at the First Pause.
23. Review the following topic and perform the procedure if applicable: Migrating Address Data from Custom Extension Columns.
24. Executing SQL Files After the First Pause.
25. Resuming the Siebel Upgrade Wizard After the First Pause.
26. Executing SQL Output Files After the Second Pause - Stage 1 of 2.
27. Deploying Stored Procedures and User-Defined Functions.
28. Executing SQL Output Files After the Second Pause - Stage 2 of 2.
29. Resuming the Siebel Upgrade Wizard After the Second Pause.
30. Executing SQL Output Files After the Third Pause.
31. Resuming the Siebel Upgrade Wizard After the Third Pause.
32. Reviewing Upgrade Log Files for Errors.
33. If the upgrade contains unacceptable errors, do the following:
    • Restore the backup of the database.
    • Correct the errors.
    • Rerun the Database Server Configuration utility.
34. Manually Archiving Upgrade Log Files.
35. Installing New License Keys After Upgrade.
36. Multilingual deployments. If you have multilingual deployments, perform the steps in 477094.1 (Article ID) on My Oracle Support. This document was previously published as Siebel Technical Note 447. This document describes how to import language-specific repository strings and seed data into the upgrade repositories.
37. Back up the upgraded database repository after a successful upgrade of the Siebel Database Schema.

Prepare for Repository Merge

38. Set the Upgrade Ancestor property for copied objects. See Configuring Objects to Inherit Upgrade Behavior.
39. Migrating Repository Objects to the Standard UI.
40. About Backing Up the New Customer Repository or Database Schema.
41. 6.2.1 upgrades only: Running the Repository Preparation Wizard on Release 6.2.1 Repository.
42. Execute the REORG utility on tables that receive a large number of inserts during the repository import process. See About Reorganizing Tables Before the Repository Merge for further information.
43. Run database statistics on the Siebel Database. For further information on running database statistics, see Updating Statistics. Running statistics on the Siebel Database improves merge performance.

    If upgrading from Release 7.7, run statistics specifically on the S_SYM_STR and SYM_STR_INT tables. If you are upgrading from a pre-7.7 release, the S_SYM_STR and SYM_STR_INT tables are not populated until the merge is completed so you do not need to run statistics on them at this point.

Perform Repository Merge

CAUTION:  The Repository merge process cannot be stopped and restarted so ensure you have backed up the database schema or the New Customer Repository before starting the merge.

44. Performing a Repository Merge.
45. Determining If a Repository Merge Was Successful.
46. If the repository merge contains unacceptable errors, do the following:
    1. Restore the backup of the database or New Customer Repository.
    2. Correct the errors.
    3. Rerun the Database Server Configuration utility.
47. Migrating Custom Workflows.
48. Back up the database.

Migrate 6.2.1 Customizations

6.2.1 upgrades only: The steps in Migrate 6.2.1 Customizations apply only to upgrades from Release 6.2.1.

49. Identifying What Will Be Migrated.
50. Exposing Hidden Properties of Applets and Views.
51. Running the Siebel Web Client Migration Wizard.
52. Reviewing Applet and View Migration.
53. Running the Web Layout Wizard.
54. Migrating Scripts Attached to Controls.
55. Migrating Scripts Attached to Applets.
56. Migrating Business Component, Business Service, and Application Scripts.
57. Migrating Outbound COM Interfaces.
58. Migrating Inbound COM Interfaces.
59. Regenerating the Postmerge Utilities Log.
60. Reviewing Customized Business Components.

Perform Postmerge Tasks

61. Running the Postmerge Utilities.
62. (Optional.) Compile an SRF file to help review the UI. See Creating a New SRF File.
63. Reviewing Attribute Conflicts in the Repository Merge.
64. Perform the tasks in Postmerge Development Tasks.
65. Generating EIM Temporary Columns After a Repository Merge.

Upgrade Physical Custom Database Schema (upgphys)

You must now upgrade the physical custom database schema.

66. Run the Database Server Configuration utility on the midtier and enter appropriate values to configure the Database Server to run the physical schema upgrade:
    • Preparing to Run the Database Server Configuration Utility.
    • Running the Database Server Configuration Utility Under Windows.
    • Running the Database Server Configuration Utility Under UNIX.

      When running the Database Server Configuration utility, choose the following settings:

    • Upgrade Options: Upgrade Siebel Database Schema (upgphys)
    • Environment Type: Development
67. Enter Yes to launch the Siebel Upgrade Wizard. SQL commands are executed on the development environment database until the Upgrade Wizard stops at the First Pause.
68. Run the files generated by the Upgrade Wizard as described in Synchronizing the Schema.
69. Dedup Files.
70. Migrating Custom Business Component Configurations.
71. Reviewing Upgrade Log Files for Errors.
72. If the upgrade contains unacceptable errors, do the following:
    1. Restore the backup of the database.
    2. Correct the errors.
    3. Rerun the Database Server Configuration utility.
73. Manually Archiving Upgrade Log Files.
74. Back up the upgraded database.
75. Deleting Redundant Upgrade Files.
76. Creating a New SRF File.

Postupgrade Tasks for Environment Setup

77. Updating File System Attachments.
78. Generate a Siebel Remote database template file. See Siebel Remote and Replication Manager Administration Guide and Regenerating the Database Template File.
79. Extract developers' databases. See Siebel Remote and Replication Manager Administration Guide and Extracting Developers or Siebel Tools Clients.
80. Initialize the local database on development machines.
81. Checking for Inactivated EIM Table Columns.
82. Reset upgrade-specific parameters back to their defaults. See Resetting Database Server Configuration Parameters.
83. Run database statistics. For more information, see Migrating Custom Business Component Configurations.

NOTE:  The development environment is now upgraded. The remaining sections deal with configuration and validation tasks.

Postupgrade Tasks for Configuration

84. Reviewing Deleted Objects in the Repository Merge.
85. Reviewing Obsolete Objects in the Repository Merge.
86. Resolve any business component and join conflicts.
87. Reapplying Custom Columns to the Siebel Database.
88. Deleting Duplicate EIM Mappings.
89. Deleting Unneeded Repository Files.
90. If you exported data from interface tables before the upgrade, review the database and import the data as desired.
91. Upgrading to RC2 or AES Encryption.

Configure for Globalization

92. Install language packs for new languages. See the Siebel Installation Guide for the operating system you are using.
93. Upgrading to the Symbolic String Model.
94. Setting Up Your Environment to Support Global Time Zone.

Deploy Workflows

Activate and deploy workflows. To perform these tasks, see Siebel Business Process Designer Administration Guide.

95. Upgrading Seeded Workflows.
96. Upgrading Inbound Workflows.

Verify Application Integration

97. Verify that EAI and EIM integrations are set up correctly. For information on using EAI and EIM, see Overview: Siebel Enterprise Application Integration and Siebel Enterprise Integration Manager Administration Guide.
98. Updating Enterprise Application Integration (EAI) After Upgrade.

Postupgrade Tasks for Application Administration

99. Review the results of the Person and Organization merge. Make configuration changes as required.
100. Generating Reporting Relationships After Upgrade.

Perform System Tests

101. Perform the tasks in Postupgrade Tasks for Applications as needed to upgrade test data in the development environment.
102. Use available test data to perform unit testing. Validate application function in the following areas:
     • User interface
     • Data interfaces
     • Integrity of migrated data
     • Workflow function
103. If you revise repository objects or schema definitions, regenerate the schema.dll and custrep.dat files. See Regenerating the Repository Definition Files.