Siebel Anywhere Administration Guide > Planning and Preparing to Use Siebel Anywhere > Determining Your Upgrade Requirements >
Determining Version-Setting Values
The exact set of information needed for defining a Siebel Anywhere upgrade kit depends on the upgrade kit's component types. However, you must supply version information for all upgrade kits. When determining who can, or 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. This topic is part of Determining Your Upgrade Requirements. For each upgrade kit, you must supply values or approve the default values for the following version settings:
- New Version
- Minimum Old Version
- Maximum Old Version
For a general discussion of the significance of these version numbers, see About Siebel Anywhere Version Settings. 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 About Existing Component Versions
The following procedure provides instructions for listing the components currently available in your Siebel Business Applications implementation, along with information about currently acceptable versions of those components and how those versions are checked. When implementing upgrades, you must 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 might have default version numbers set to 0 (zero). If the version number of a new component is left lower than the version number of the corresponding preupgrade component, then newly upgraded users might 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. The version number of your repository is displayed as User Version when you choose Help, then About Repository, in your Siebel application. For more information about using srfstamp, see Testing the Consistency of Upgrade Kit Components. To display version information for existing components
- Navigate to the Administration - Siebel Anywhere screen, then the Upgrade Component List view.
The Upgrade Component List appears. Table 8 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 must modify version information for an existing component, then use the Upgrade Kit Wizard, as described in Defining Upgrade Kits. If you want to modify other component characteristics, then create a custom component with the characteristics that you need, as described in Setting Up Custom Siebel Anywhere Upgrade Components.
Table 8. Fields in the Upgrade Component List
|
|
Component Type |
The type of component for upgrade kits; for example, Siebel Repository File or Third Party Software. |
Locate Information |
Information used by Siebel Anywhere when locating version information for the subscriber's currently installed component. For more information about how Siebel Anywhere uses this setting, see About Monitoring and Verifying Siebel Anywhere Version Numbers. |
Locate Method |
The method used by Siebel Anywhere to locate version information for the subscriber's currently installed component. For more information about how Siebel Anywhere uses this setting, see About Monitoring and Verifying Siebel Anywhere Version Numbers. |
Max Version |
The latest version of the component that is available for running the application in read and write mode. |
Min Version |
The earliest version of the component that is acceptable for running the application in read and write mode. |
Name |
The name that identifies the component for Siebel Anywhere. |
Version Information |
Information used by Siebel Anywhere when checking the version of the subscriber's currently installed component. For more information about how Siebel Anywhere uses this setting, see About Monitoring and Verifying Siebel Anywhere Version Numbers. |
Version Method |
The method used by Siebel Anywhere to check the version for the subscriber's currently installed component. For more information about how Siebel Anywhere uses this setting, see About Monitoring and Verifying Siebel Anywhere Version Numbers. |
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 must supply values for the New Version, Minimum Old Version, and Maximum Old Version settings.
The following tables contain guidelines for determining the version values to use in a variety of situations.
- Table 9 provides guidelines for choosing your New Version value.
- Table 10 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 for each component. 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 9 to find a description of your situation, and read the adjacent guidelines for setting the appropriate value.
Table 9. New Version Planning Worksheet for Upgrade Component
|
|
|
|
New Version (Identifies the version number of the component in the upgrade kit) |
New component |
Set New Version to 1. |
1 |
Upgrade to existing component |
Set New Version to n plus 1, where n is the Siebel Anywhere version number of the latest version of the component previously installed within your Siebel Business Applications implementation. To display previously installed versions, see Gathering Information About Existing Component Versions. |
___ |
Upgrade to existing component after a major Siebel upgrade |
Make sure that any components provided in the major upgrade have Siebel Anywhere version numbers equal to or greater than preupgrade components. You might need to stamp new numbers on the components to achieve this, particularly for SRF files. For more information, see Testing the Consistency of Upgrade Kit Components. When component version numbering is continuous for the upgrade, use the instructions for upgrading to an existing component, in the previous row of this table. |
___ |
Replacing a defective upgrade kit that has been distributed and deactivated |
Set New Version to the same value you assigned to the defective upgrade kit. |
___ |
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 10 to find a description of your situation, and read the adjacent guidelines for setting the appropriate values.
Table 10. Minimum and Maximum Old Version Planning Worksheet for Upgrade Component
|
|
|
|
Minimum Old Version (Determines who can use the upgrade kit) |
No component versions are prerequisites for subscribers using upgrade kit or all needed prerequisites are included in this upgrade kit. |
Leave blank. |
NULL |
Subscribers are upgrading a history-independent component, such as SRF, executable, or Siebel database schema. |
This setting is automatically set to NULL. It cannot be changed. |
NULL |
Subscribers are upgrading a CFG file. |
It is recommended that you leave this setting blank. |
___ |
Subscribers are upgrading a customer revision component. |
It is recommended that you accept the default value for this setting and the setting for Maximum Old Version, to make sure that your users download and install every upgrade kit of this type, without skipping any of them. |
___ |
Subscribers are required to have a prior version of component. |
Set to the earliest component version that can download and install the new upgrade kit. |
___ |
You are replacing a defective upgrade kit that has been distributed and deactivated. |
Set Minimum Old Version to the same value as you used in the defective upgrade kit. |
___ |
Maximum Old Version (Determines who can use the upgrade kit) |
No component versions are prerequisites for subscribers using upgrade kit or all needed prerequisites are included in this upgrade kit. |
Leave blank. |
NULL |
Subscribers are upgrading a history-independent component, such as SRF, executable, or Siebel database schema. |
This setting is automatically set to NULL. It cannot be changed. |
NULL |
Subscribers are upgrading a CFG file. |
It is recommended that you leave this setting blank. |
___ |
Subscribers are upgrading a customer revision component. |
It is recommended that you accept the default value for this setting and the setting for Minimum Old Version, to make sure that your users download and install every upgrade kit of this type, without skipping any of them. |
___ |
Subscribers are required to have a prior version of component. |
Set to the latest component version that can download and install the new upgrade kit. This value is always less than the value of New Version. |
___ |
You are replacing a defective upgrade kit that has been distributed and deactivated. |
Set Maximum Old Version to the same value as you used in the defective upgrade kit. |
___ |
|