Distributing Upgrade Kits

After applying an upgrade kit, you must distribute it to one or more configurations. For general information about configurations, see Upgrade Configurations.

This task is a step in Process of Completing Upgrade Kit Creation

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

Upgrade kits are distributed to one configuration at a time. The distribution process makes the upgrade kit's component version information available to all the subscribers who are associated with that configuration, giving the subscribers their first opportunity to download and install the upgrade kit. Neither required nor optional upgrade kits are available to subscribers until the version information is distributed.

The version information that is made available during the distribution process includes version information for all the related components of the configuration, not just the component that the new upgrade kit is designed to upgrade. Technically, therefore, when you distribute a new upgrade kit to a configuration, you make that upgrade kit's version information available to the configuration, and you redistribute the version information of other active upgrade kits for the configuration's related components. In practice, however, you generally can proceed as if you were distributing only the one upgrade kit.

After distribution, if the upgrade kit is required, then subscribers are automatically prompted to retrieve and install it. If the upgrade kit is optional, then subscribers use the Component Upgrades view and Upgrade Wizard to locate and install the upgrade kit.

Caution: Before you distribute an upgrade kit, you must define, activate, and apply it. Before you distribute an upgrade kit to any configuration containing production users, it is strongly recommended that you use the Siebel Test Client configuration to test the upgrade kit thoroughly. It is particularly important to test any required upgrade kit before distributing for general use, because Mobile Web Client users can suffer unnecessary delays while downloading a defective required upgrade kit, and they can lose read and write access to Siebel Business Applications until a correctly functioning upgrade kit is available.

The following procedure describes how to distribute an upgrade kit from the Upgrade Configurations view. The same procedure can also be performed from the Employees view.

Note: There are additional instructions for distributing Siebel Database Schema upgrade kits. For information, see Process of Updating the Siebel Database Schema.

To distribute an upgrade kit

Navigate to the Administration - Siebel Anywhere screen, then the Upgrade Configurations view.
In the Upgrade Configurations view, select the appropriate Anywhere subscriber configuration.
Inspect the Upgrade Components list to verify that the components in the upgrade kit are related components for the selected configuration.

For example, for a Siebel Innovation Pack release, the related components must include the Siebel Client Executables component for the base upgrade kit.
Click Distribute.

This action makes the version information in the database available to subscribers with that particular configuration.

A dialog box appears to confirm the intent to distribute the related components to the configuration.
Repeat the previous steps for other configurations, as applicable.

For more information about special cases of distribution, see: