Testing the Consistency of Upgrade Kit Components

After you upgrade a Siebel application to a new release, check to make sure that version numbering continues for the releases for upgrade components in each Siebel Anywhere configuration. Upgrading to a new release of Siebel Business Applications upgrades the Siebel Anywhere table definitions. However, it does not reset the Upgrade Component information for Siebel Anywhere configurations.

As a result, Siebel Anywhere will resume version checking against the existing component versions in the new release of Siebel Business Applications. If required upgrade kits for Siebel Client Repository Export Import, Siebel Client Customer Revisions, or Siebel CFG File were distributed in the previous release, then newly upgraded production clients might be incorrectly prompted for upgrade kits when they synchronize with the server.

Before upgrading production users, test the upgrade kit on a Siebel administrator's client with version checking enabled. Verify that this client passes version check, so that after the upgrade kit is packaged and distributed, it will function correctly for the remainder of your production users.

To accomplish this testing, verify that the administrator's client has the latest versions for Siebel Repository Export Import, Siebel Client Customer Revisions, and Siebel CFG__language-code.

The following procedures describe how to test Siebel Client Customer Revisions and CFG file components for consistency.

To test Siebel Client Customer Revisions components for consistency

Copy the clntrev.cfg file from one of your previous release production clients to the SIEBEL_CLIENT_ROOT\BIN directory of the Siebel administrator's client.

To test Siebel CFG file components for consistency

Edit the appropriate CFG file under SIEBEL_CLIENT_ROOT\BIN\language-code and increment the Version parameter in the [Siebel] section to the Maximum Version of the Upgrade Component Siebel Call Center CFG file for the previous release.