Upgrade Component

Drop-down list

Name of the component the upgrade kit will install or upgrade. Select one of the following:

• Siebel Client Repository File_[language-code] (use when distributing repository file to clients)
• Siebel Server Repository File_[language-code] (use when distributing repository file to servers)

Select File Type

Radio button

Specifies whether the kit will contain a complete repository file or a "delta" repository file. Select one of the following values:

• Standard Repository File. Use this file type when defining a repository upgrade kit for clients if the kit will contain a complete repository file. For a repository upgrade kit for a server, always choose this file type.
• Delta Repository File. Use this file type when defining an upgrade kit for clients if the kit will contain a "delta" repository file. A delta repository file contains information about changes to a specific version of a complete repository file, rather than the complete file, itself. The delta repository file must be created ahead of time, using the Siebel Delta SRF Utility (diffsrf). For information about creating the delta repository file, see Process of Creating a Delta Repository File Upgrade Kit.

Files to Add

Text field

Universal Naming Convention (UNC) path and file name of the delta .srf file to include in a Delta Repository File upgrade kit. Browsing is available by clicking the Browse button described in the following row of this table.

Browse

Button

Displays a standard dialog box for browsing and choosing a delta .srf file. Available for Delta Repository File upgrade kits only.

UNC Path for SRF file

Text field

Universal Naming Convention (UNC) path and file name of the standard (complete) .srf file to include in a Standard Repository File upgrade kit. Browsing is not available for Standard Repository File upgrade kits.

Minimum Old Version

Read-only text field

Earliest component version that can download and install the upgrade kit. Automatically set to NULL for history-independent component types, including repository files, indicating that there are no prerequisite versions required for using the kit. For more information about choosing version values, see Determining Version Setting Values.

Maximum Old Version

Read-only text field

Latest component version that can download and install the upgrade kit. Automatically set to NULL for history-independent component types, including repository files, indicating that there are no prerequisite versions required for using the kit. For more information about choosing version values, see Determining Version Setting Values.

Base Version

Text field

For a delta Repository File upgrade kit, specifies the version number of the repository file that was used as a base for the changes that the delta kit will distribute.

To determine the version number of the base repository file, open a command window, navigate to SIEBEL_ROOT\bin or SIEBEL_CLIENT_ROOT\bin, and enter the following command, substituting the name of the base repository file and the language code used for that repository:

srfstamp /r repository_file_name /l language-code

New Version

Text field

Version number that the component being upgraded will have after the upgrade kit is installed. Default value is 1 greater than the current version for the component to be upgraded. For a Siebel Repository File upgrade kit, the New Version Value must be an integer. For more information about choosing version values, see Determining Version Setting Values.

Activate Upgrade Kit

Check box

When this check box is selected, the files to be included in the upgrade kit will be compressed into a single archive on the Siebel File System automatically. Activation can also be performed manually, as described in Activating, Applying, and Distributing Upgrade Kits.

For most upgrade kits, it is recommended that you select this check box. However, if you are creating an upgrade kit that is dependant on another upgrade kit, be sure to clear this check box. (For example, a repository kit might be dependent on a database schema kit.) For information about working with dependent kits, see Controlling the Order of Kit Installation.

Apply Versions

Check box

Displayed only if Activate Upgrade Kit check box was selected in an earlier Upgrade Kit Wizard screen. When this check box is selected, the compiled information string in the database will be updated automatically with the component version information for this upgrade kit. Applying versions can also be performed manually, as described in Activating, Applying, and Distributing Upgrade Kits.

For most upgrade kits, it is recommended that you select this check box. However, if you are creating an upgrade kit that is dependant on another upgrade kit, be sure to clear this check box. For information about working with dependent kits, see Controlling the Order of Kit Installation.

Required Upgrade Kit

Check box

When this check box is selected, the upgrade kit will be required regardless of previous versions installed. (Min Version and Max Version are set equal to New Version, but this change is not visible in the Upgrade Kit Wizard.) Displayed only if Apply Versions check box was selected in an earlier Upgrade Kit Wizard screen.

Upgrade Kit Title

Text field

Identifier for the upgrade kit. Defaults to Upgrade Component Name value followed by a space and the New Version value, but can be modified during the kit definition process. After the kit is defined, this identifier appears in the Name field of the Upgrade Kits list.

Comments

Text field

Available for comments about the upgrade kit. Comments entered here are displayed in the Upgrade Kits list.