Upgrade Guide for DB2 UDB for z/OS > Upgrading a Development Environment Database from the Midtier >

Migrating Custom Business Component Configurations

Upgrades: Release 6.2.1 of Siebel Financial Services applications.

Environments: Development environment only.

This topic is part of an upgrade process. See How to Perform the Upgrade.

Customized business component configurations (buscomps) which are based on customer extension columns or on Siebel columns in obsolete tables need to be identified and manually fixed after the upgrade. Siebel columns in obsolete tables are reconfigured and migrated during the upgrade. However, customer buscomps or custom extension columns on obsolete tables need to be migrated manually.

NOTE:  Custom extension columns on tables that are upgraded (not obsolete) are retained during the upgrade.

To review a list of the buscomps that require manual migration, review the upgcust.log file, located in the SIEBSRVR/log directory.

Critical obsolete tables are listed in Table 24.

The access control buscomp migration utility is run on the Prior Customer Repository by the Siebel Upgrade Wizard during upgrade of the Siebel Database schema.

Several fields, buscomps, and columns may need to be reevaluated and recreated after your upgrade. A sample conversion script is available for migration of data to the new columns during the development upgrade.