Bookshelf Home | Contents | Index | PDF     

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

Process of Upgrading a 7.x Development Environment from the Mainframe

Upgrades: Releases 7.0.x, 7.5.x, 7.7.x.

Environments: Development (mainframe-centric) environment.

This process is part of an upgrade road map. See the road maps earlier in this chapter.

This topic lists the steps required to upgrade a 7.x development environment from the mainframe to a production environment. 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.

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.

To perform the following steps, see the Siebel Installation Guide for the operating system you are using.

  1. 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.
  2. Install the Siebel Gateway Name Server, Siebel Servers, and Siebel Web Server Extension (SWSE). In many cases, you do not have to uninstall the Siebel Servers or SWSE before installing the new versions.
  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.

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

Upgrade Third-Party Software

  • 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.

Upgrade the RDBMS

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

Preupgrade Tasks for the Siebel Database Upgrade

These steps apply to all database types.

  1. 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.
  2. Review 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.
  3. Review guidelines for configuring the RDBMS. See the Siebel Installation Guide for the operating system you are using.
  4. Verify all developers have checked in their projects.
  5. Verify that the Workflow Monitor and Workflow action agents have processed all pending requests.
  6. Stop the Siebel Server and the Siebel Gateway Name Server.
  7. Verify there are no open database connections.
  8. Preparing Tables and Views for Upgrade.
  9. Preparing Custom Indexes for Upgrade.
  10. Exporting Interface Table Data.
  11. Preserving Dock Objects and Visibility Rules.
  12. Verifying Database Server Configuration.
  13. Securing AIX Memory Allocation Segment Space.
  14. Creating Storage Groups.
  15. Preparing the Storage Layout of the Schema.
  16. Reviewing Tablespace Size.
  17. Backing Up the Database.
  18. Adding a Siebel User.

Preupgrade Tasks for DB2 UDB for z/OS

  1. Prerequisites for a Development Upgrade.
  2. Checking In Development Repository Projects.
  3. Saving Interface Table Data.
  4. Upgrading Your DB2 Software.
  5. Preparing EIM Tables for Upgrade.
  6. Preparing for Intersection Table Maintenance and Deduplication.
  7. Determining Which Template File was Used During an Extract or Merge.
  8. Disabling Customized Triggers.
  9. Dropping Customized Views.
  10. Preparing the Development Environment Repositories for Upgrade.

Preupgrade Tasks for Application Data

  1. Preparing Workflow Processes for Upgrade.
  2. Preparing Mobile and Dedicated User Data for the Database Upgrade.

The remaining tasks are optional depending on currently installed Siebel products and whether the data in the development environment needs to be preserved or upgraded. Review and perform these tasks as necessary.

  1. Setting Up Campaign Status Values for Siebel Marketing Upgrade.
  2. Preparing Address Data for Upgrade.
  3. Preparing Products for Upgrade.
  4. Preserving Marketing Segment Descriptions.
  5. Preparing Siebel eChannel Data for Upgrade.
  6. Preparing Forecasting Data for Upgrade.
  7. Preparing Products and Quotes for Upgrade.
  8. Verifying Household Data Integrity.
  9. Preparing Financial Services Application Tables for Upgrade.
  10. Preparing Siebel Configurator Data for Upgrade.

Upgrade Siebel Database Schema (upgrep)

  1. Back up the development database. (If you backed up the database as part of an RDBMS upgrade, ignore this step.)
  2. Renaming the Tools Repository.
  3. Run the Database Server Configuration utility:
  4. Review the following topic and perform the procedure if applicable: Migrating Address Data from Custom Extension Columns.
  5. Transferring the Customized Repository to z/OS Host.
  6. Preparing the zSeries Host Environment.
  7. Resuming the Siebel Upgrade Wizard After the First Pause.
  8. Transferring Control Cards and Schema DDL Files to the zSeries Host.
  9. Preparing the Schema and JCL Files on the zSeries Host.
  10. Installing Stored Procedures on the zSeries Host.
  11. Preparing Siebel-Scheduled Jobs on the zSeries Host.
  12. Optimizing the Source Database Job Stream.
  13. Optimizing the Source Database Job Stream.
  14. Loading Log Tables on the Source Database.
  15. Loading Log Tables on the Target Database.
  16. Executing the Upgrade on the zSeries Host (Phase 1 of 2).
  17. Resuming the Siebel Upgrade Wizard on the Midtier After the Second Pause.
  18. Transferring the Index Schema to the zSeries Host.
  19. Preparing Siebel-Scheduled JCL.
  20. Executing the Upgrade on the zSeries Host (Phase 2 of 2).
  21. Performing Intersection Table Maintenance.
  22. Reviewing Upgrade Log Files for Errors.
  23. 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.
  24. Manually Archiving Upgrade Log Files.
  25. Installing New License Keys After Upgrade.
  26. Back up the upgraded database.

Prepare for Repository Merge

  1. Set the Upgrade Ancestor property for copied objects. See Configuring Objects to Inherit Upgrade Behavior.
  2. Migrating Repository Objects to the Standard UI.
  3. Run database statistics on the Siebel Database. If upgrading from Release 7.0.x or 7.5.x, run statistics specifically on S_SYM_STR and SYM_STR_INT. Also, see Generating RUNSTATS.

    Running statistics on the Siebel Database improves merge performance.

Perform Repository Merge

  1. Performing a Repository Merge.
  2. Determining if a Repository Merge was Successful.
  3. If the repository merge contains unacceptable errors, do the following:
    1. Restore the backup of the database.
    2. Correct the errors.
    3. Rerun the Database Server Configuration utility.
  4. Back up the database.

Run the Postmerge Utilities

  1. Running the Postmerge Utilities.
  2. (Optional.) Compile an SRF file to help review the UI. See Creating a New SRF File.
  3. Reviewing Attribute Conflicts in the Repository Merge.
  4. Troubleshooting Postmerge UI Problems.
  5. Verifying Business Address Applet Configuration.
  6. Reviewing Grid-Based Applets After the Merge.
  7. Reviewing UI Navigation After the Merge.
  8. Reviewing Multi-Value Group (MVG) Shuttle Applets After the Merge.
  9. Revising Rich Text Controls After the Merge.
  10. Reviewing New Aggregate Categories After the Merge.
  11. Revising Visibility Filters to Display Correctly After the Merge.
  12. Assigning a Category and Type to Chart Views After the Merge.
  13. Assigning a Category and Type to Explorer Views After the Merge.
  14. Setting Up Navigation to Inaccessible Detail Views After the Merge.
  15. Eliminating Obsolete UI Fields After the Merge.
  16. Reviewing UI Objects Affected by ICL After the Merge.
  17. Reviewing Required Fields in the UI After Merge.
  18. Setting Label Alignment for Text Fields.
  19. Assigning an Item Identifier to Web Template Items.
  20. Generating EIM Temporary Columns After a Repository Merge.

Upgrade Custom Database Schema (upgphys)

  1. Run the Database Server Configuration utility:
  2. Reviewing Upgrade Log Files for Errors.
  3. 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.
  4. Manually Archiving Upgrade Log Files.
  5. Back up the upgraded database.

Postupgrade Tasks for Environment Setup

  1. Updating File System Attachments.
  2. Creating a New SRF File.
  3. Generate a Siebel Remote database template file. See Siebel Remote and Replication Manager Administration Guide and Regenerating the Database Template File.
  4. Extract developers' databases. See Siebel Remote and Replication Manager Administration Guide and Extracting Developers or Siebel Tools Clients.
  5. Initialize the local database on development machines.
  6. Checking for Inactivated EIM Table Columns.
  7. Reset upgrade-specific parameters back to their defaults. See Resetting Database Server Configuration Parameters.
  8. Run database statistics. For more information, see Generating RUNSTATS.

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

Postupgrade Tasks for Configuration

  1. Reviewing Deleted Objects in the Repository Merge.
  2. Reviewing Obsolete Objects in the Repository Merge.
  3. Reviewing Customized Business Components.
  4. Reapplying Custom Extensions and FK Columns on Obsolete Tables.
  5. Resolving Business Component and Join Conflicts.
  6. Deleting Unneeded Repository Files.
  7. If you exported data from interface tables before the upgrade, review the database and import the data as desired.
  8. Upgrading to RC2 or AES Encryption.
Configure for Globalization
  1. Install language packs for new languages. See the Siebel Installation Guide for the operating system you are using.
  2. Upgrading to the Symbolic String Model.
  3. Setting Up Your Environment to Support Global Time Zone.
Deploy Workflows

To perform these tasks, see Siebel Business Process Designer Administration Guide.

  1. Activate and deploy workflows. See Siebel Business Process Designer Administration Guide.
  2. Upgrading Seeded Workflows.
  3. Upgrading Inbound Workflows.
Verify Application Integration
  1. 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.
  2. Updating Enterprise Application Integration (EAI) After Upgrade.

Postupgrade Tasks for Application Administration

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

Perform System Tests

  1. Perform the tasks in Postupgrade Tasks for Applications as needed to upgrade test data in the development environment.
  2. 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
  3. If you revise repository objects or schema definitions, regenerate the schema.dll and custrep.dat files. See Regenerating the Repository Definition Files.
    
Upgrade Guide for DB2 UDB for z/OS and OS/390