Siebel Anywhere Administration Guide > Upgrade Planning and Preliminary Tasks > Determining Upgrade Requirements >

Determining Version Setting Values

The exact set of information needed for defining a Siebel Anywhere upgrade kit depends on the type of kit involved. However, you must supply version information for all upgrade kit types. When determining who can and who must upgrade a particular component, Siebel Anywhere compares version information stored in the database with the versions of components actually installed on each subscriber's computer. The information in the database comes from the information you supply when you create upgrade kits.

For each upgrade kit, you will need to supply values or approve default values for three version settings:

• New Version
• Minimum Old Version
• Maximum Old Version

For a general discussion of the significance of these versions, see How Siebel Anywhere Versions Work. In general, the values you supply will be related to the version numbers already in use for the component being upgraded. Therefore, gathering version information about existing components is an important part of planning an upgrade.

CAUTION:  Make certain that Minimum Old Version, Maximum Old Version, and New Version settings are correctly set before finishing your upgrade kit, using the default numbering system, if possible. Incorrectly specifying the version information can prevent subscribers from upgrading successfully.

Gathering Information on Existing Component Versions

The following procedure provides instructions for listing the components currently available in your Siebel implementation, along with information about currently acceptable versions of those components and how those versions are checked.

CAUTION:  When implementing major upgrades, be sure to preserve the version numbers for every component. This precaution is important because Siebel Anywhere assigns increasing version numbers, but components that are included in upgrades may have default version numbers set to zero. If the version number of a new component is left lower than the version number of the corresponding preupgrade component, newly-upgraded users may be prompted, incorrectly, to install the old component. Never reset any Siebel Anywhere version numbers to zero; instead, increase the version numbers of the new components to match their preupgrade counterparts. In particular, you must use the srfstamp utility to stamp a current version number on a new repository (.srf) file. For information about using srfstamp, see To test repository components for consistency. The version number of your repository is displayed as User Version when you choose Help > About Repository from the application-level menu in your Siebel application.

To display version information for existing components

1. From the application-level menu, select Navigate > Site Map > Administration - Siebel Anywhere.
2. From the link bar, select Upgrade Component List.

   The Upgrade Component List appears. Table 7 describes the information available in this list.

   CAUTION:  Do not use the Upgrade Component List to modify information about an existing component—modifying information in the list can prevent version checking from working properly. If you need to modify version information for an existing component, use the Upgrade Kit Wizard, as described in Defining Upgrade Kits. If you want to modify other component characteristics, create a custom component with the characteristics you need, as described in Setting Up Custom Siebel Anywhere Upgrade Components.

Planning Version Settings for a New Upgrade Kit

The information you gather about current version settings lets you plan version settings for your new upgrade kit.

NOTE:  When you run the Upgrade Kit Wizard to define your new upgrade kit, you will need to supply values for the New Version, Minimum Old Version, and Maximum Old Version settings.

The following tables contain guidelines for determining the version values you should use in a variety of situations.

• Table 8 provides guidelines for choosing your New Version value.
• Table 9 provides guidelines for choosing your Minimum Old Version and Maximum Old Version values.

You can use these tables as worksheets by printing them out and filling in the values that you will use when you define your upgrade kit.

The New Version value specifies the version number that the component being upgraded will have after the upgrade kit is used. Look in the Situation column of Table 8 to find a description of your situation, and read the adjacent guidelines.

The Minimum Old Version and Maximum Old Version values specify the range of component versions that subscribers must have to download and install the upgrade kit. Look in the Situation column of Table 9 to find a description of your subscribers' situation, and read the adjacent guidelines for choosing values.