Bookshelf Home | Contents | Index | PDF |
Upgrade Guide > How the Siebel Database Upgrade Works > About the Siebel Postmerge UtilitiesUpgrades: All Siebel upgrades. Environments: Development environment only. You run the postmerge utilities after the repository merge completes. The postmerge utilities make revisions to objects in the New Customer Repository. The utilities are intended primarily to identify UI configuration problems for upgrades prior to Siebel 7.7. (At Siebel 7.7, there were significant changes to UI navigation.) The utilities are also useful for identifying problems with UI customizations for upgrades after Siebel 7.7. The postmerge utilities are implemented as a framework. Each utility in the framework is a business service and is listed in Windows UNIX: SIEBEL_TOOLS_INSTALL_DIR is the directory where Siebel Tools is installed. The postmerge utilities are as follows:
CSSGridRepPatchAs of Siebel 7.7, the layout of form applets is grid-based, rather than flow-based. Applet Form Web templates have several new properties: Grid Property, Row Span, and Col Span. In addition, item identifier syntax changes to xxyyy, where xx is the grid row and yyy is the grid column where the control is located. Regular merge. The utility identifies both customer-created and customer-modified applets and adjusts the properties of controls in them as follows:
ICL merge. (Applies only to applets where Upgrade Behavior is not set to Admin.) For upgrades from releases prior to 7.7, form applets copied-in from the Prior Customer Repository remain flow-based and display normally. The utility does not convert these applets to grid-based. New and modified controls display in the correct locations. For upgrades from Siebel 7.7 or later, the utility makes no changes. The utility logs output to the CSSUINavUpgradeReposPrepAt Siebel 7.7, a declarative model for associating views with screens was introduced. The relationship between views and screens for all levels of navigation must be explicitly declared. Several new object properties for screens and views are introduced to support this. The new navigation scheme is applied to all screens and views for both regular and ICL merges. The utility runs after the repository merge in all upgrades. However, it is intended primarily for upgrades from releases prior to 7.7. After a regular or ICL merge, screens and views display as follows:
The utility scans all screen view definitions looking for orphaned views. It groups orphaned views under existing Categories. If no Category exists, the utility creates one. This causes the orphaned views to display. For a regular merge, you must review customer-created and customer-modified screens and views to verify that views are correctly associated with screens. For an ICL merge, you must also review these screens and views. In addition, you must review all screens and views where Upgrade Behavior is set to Preserve or NULL. The utility logs output to the CSSMVGUpgradePatch77As of Siebel 7.7, MVG applets with a M:M relationship to the underlying business component are configured as shuttle applets by default. The utility scans these MVG applets in the New Customer Repository and reconfigures them to display as shuttle applets:
The utility logs output to the CSSUIUpgradeReportsThis utility makes no changes to the New Customer Repository. Instead, it scans UI objects in the repository and lists problems that could not be resolved by the CSSUINavUpgradeReposPrep utility. The CSSUIUpgradeReports utility writes the report to The report has the following sections:
CSSWebTemplatePatchThis utility runs after an ICL merge. It does not run after a regular merge. The utility performs the following steps in the installation directory of the Siebel Tools that you used to perform the merge:
CSSWFRepPatchThis utility changes workflow step references from row-id references to name references for child objects of steps. This completes the process of migrating workflows to the repository at Siebel 7.7. This utility primarily affects upgrades from releases prior to Siebel 7.7. This utility does not write to the reputility.log. How the Postmerge Utilities Work the Upgrade Behavior PropertyThe postmerge utilities ignore the Upgrade Behavior property. They make changes to UI objects based on the object's characteristics rather than Upgrade Behavior setting. Related Topics |
Upgrade Guide | Copyright © 2006, Oracle. All rights reserved. | |