1. Anywhere Administration Guide
  2. About Specifying the Versions That Can Use the Upgrade Kit

About Specifying the Versions That Can Use the Upgrade Kit

The Siebel administrator who creates an upgrade kit also specifies which previous versions of the component are compatible with the upgrade kit. If one or more specific versions are specified, then a client or server must already have one of those versions to download and use the upgrade kit.

The following Upgrade Kit Wizard settings are used to specify the acceptable range of versions for downloading the upgrade kit:

  • Minimum Old Version

  • Maximum Old Version

These settings are specified as part of the process of defining the upgrade kit. For more information about defining upgrade kits, see Defining Upgrade Kits.

As an example, suppose you assign the following values when creating a customer revision upgrade kit. (These values might be suitable when New Version is set to 3 for the upgrade kit.)

  • Minimum Old Version = 1

  • Maximum Old Version = 2

These example values cause the following results:

  • Mobile Web Clients with version 0 of the customer revision component cannot download the upgrade kit until they execute an upgrade kit that changes their customer revision number from 0 to either 1 or 2.

  • Mobile Web Clients with version 1 or 2 of the customer revision component can download the upgrade kit.

As a second example, suppose you assign the following values when creating an upgrade kit for a custom component:

  • Minimum Old Version = NULL

  • Maximum Old Version = NULL

Null values for both of these settings indicate that subscribers who have any previous version of the component, or no previous version of the component, can download and use the upgrade kit. Use null values for these settings only if there are no prerequisite versions for the component, or if the upgrade kit will contain all prerequisites within itself.

As a third example, suppose you want to distribute two upgrade kits for the same custom component, such as a report and a batch file that will manipulate the report. To make sure that the report is installed before the batch file runs, you would create one upgrade kit for the report and a second upgrade kit for the batch file, and you would make the upgrade kit for the batch file dependent on the upgrade kit for the report. The following table lists the settings that would accomplish this objective.

Upgrade Kit Description

Minimum Old Version Value

Maximum Old Version Value

New Version Value

Report (upgrade kit #1)

NULL

NULL

1

Batch file to manipulate the report (upgrade kit #2)

1

1

2