Bookshelf v7.5: Applying an Upgrade Kit

Siebel Anywhere Administration Guide > Activating, Applying, and Distributing Upgrade Kits >

Applying an Upgrade Kit

After you activate the upgrade kits for an upgrade, you need to apply each kit. Applying a kit updates the compiled information string in the database with the component version information. This is an essential step in creating an upgrade kit. This is also the step in which you indicate whether a kit is a required upgrade kit.

This task is a step in Process of Completing Upgrade Kit Creation and in Process of Limiting Distribution of an Upgrade Kit.

Upgrade.ucf is the driver file for the Upgrade Wizard to apply the upgrade kit. It contains an ordered list of action items for the Upgrade Wizard to execute during the installation of the upgrade kit.

The following procedure describes how to apply an upgrade kit. This updates the compiled information string in the database with the component version information.

NOTE: If a replacement kit uses the same values for New Version, Minimum Old Version, and Maximum Old Version as the deactivated kit it replaces, and if the deactivated kit was previously distributed, you do not need to apply or distribute the replacement kit.

To apply an upgrade kit

Navigate to the Anywhere Administration screen, and from the Show drop-down list, click Upgrade Kits.

The Upgrade Kits view appears.

Select the kit you want to apply.

The Status field must show that it is Active.

Click Apply Versions.

The Apply Upgrade Kit Version Information dialog box appears, as shown in the following figure. Review the information in this dialog box. The paragraphs following the figure provide additional information.

The Min Version and Max Version numbers in this dialog box apply to the version of the component that can be used to bring up the application in read/write mode. If users have a version below the minimum and choose not to install the upgrade, they can only access the application in a read-only mode.

If you click OK without clicking Require Upgrade Kit, you are making it an optional kit (that is, after the kit is distributed, your subscribers can use Siebel eBusiness Applications without upgrading—provided their version is between the minimum and maximum).

If you click Require Upgrade Kit, the minimum version changes to match the maximum version, which is the new version. In this case, the subscribers will have to upgrade after the configuration is distributed; otherwise, they can only bring up the application in a read-only mode.

NOTE: It is strongly recommended that you create upgrade kits as optional and then test to make sure the kit is functioning properly. After you thoroughly test a kit using retrieval and installation, you can return to the Upgrade Kits view and reapply and distribute the kit as a required kit. See Distributing Upgrade Kits for more information.

Click OK if the version information is correct or click Cancel to exit the dialog box without applying the upgrade kit.

If you click OK, a prompt reminds you that you need to distribute the kit to make it available to subscribers. For information on distributing kits, see To distribute an upgrade kit.

Repeat Step 2 through Step 4 for each kit in this upgrade. Continue to Distributing Upgrade Kits for distributing updated version information for upgrade kits.

NOTE: If there are multiple kits of the same type that are either SRF, Database Schema, or Client Executable, it is strongly recommended you deactivate the old kits. This will save time for your users by preventing the downloading of outdated kits. (The version information for a deactivated kit can be retrieved, but a deactivated kit, itself, cannot be retrieved. When a user tries and fails to retrieve a deactivated kit, an automatic attempt is made to retrieve a later kit that is currently activated.)