Bookshelf v7.5: Defining a Third-Party Software Upgrade Kit

This section provides specific instructions for defining a Third-Party software upgrade kit using the Upgrade Kit Wizard.

NOTE: Siebel Anywhere Third-Party software components are meant to support third-party software products that are needed for operation with Siebel applications. Siebel Anywhere is not a general purpose tool for software configuration management and distribution.

Information in Table 20 is presented in approximately the sequence used by the Upgrade Kit Wizard.

Table 20. Upgrade Kit Wizard Elements for a Third-Party Software Upgrade Kit
Wizard Element	Element Type	Comments
Upgrade Component	Drop-down list	Name of the component the upgrade kit will install or upgrade. Choose one of the following predefined components, or a custom component you have created: Third Party - Oracle 8 Client Third Party - Microsoft Word Third Party - Microsoft SQL Server Driver Third Party - Microsoft Internet Explorer Third Party - IBM DB2 Client Third Party - Adobe Acrobat Reader Third Party - Adobe Acrobat
UNC Path for Software Directory	Text field	Path to the directory that contains the files to include in the upgrade kit. All files in the specified directory are included in the kit automatically.
Destination Directory	Text field	Specifies where the files from the upgrade kit are to be placed on the client machine. Default value is $SiebelRoot\upgrade\$KitName, where $SiebelRoot refers to the Siebel client root directory, and $KitName refers to a subdirectory with the name of the upgrade kit. Both of these variables are case-sensitive.
Delete destination file when done	Check box	When this check box is selected, the upgrade kit files will be deleted, automatically, after the kit is installed.
Specify file to execute	Text field	Specifies the file that runs the software installer on the subscriber's computer, such as install.exe. Only one file per upgrade kit can be specified for execution. Be sure you specify a file that can be executed, such as a .bat or .exe file. If you specify a file that cannot be executed, such as a .txt file or a CFG file, the upgrade kit will not install properly.
Enter command line arguments	Text field	Specifies any command line arguments to use when running the file chosen in the Select file to execute field.
Minimum Old Version	Text field	Earliest component version that can download and install the upgrade kit. When this field is blank, indicates that there are no prerequisite versions required for using the kit. Defaults to the current component version recorded in the database. For more information about choosing version values, see Determining Version Setting Values.
Maximum Old Version	Text field	Latest component version that can download and install the upgrade kit. When this field is blank, indicates that there are no prerequisite versions required for using the kit. For more information about choosing version values, see Determining Version Setting Values.
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 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 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, or if you know that you need to specify nondefault values for Component Minimum Version or Component Maximum Version, be sure to clear this check box. For information about working with dependent kits, see Controlling the Order of Kit Installation.
Component Minimum Version	Read-only text field	Earliest component version acceptable for running the software in read/write mode. Displayed only if Apply Versions check box was selected in an earlier Upgrade Kit Wizard screen.
Component Maximum Version	Read-only text field	Latest component version acceptable for running the software in read/write mode. Displayed only if Apply Versions check box was selected in an earlier Upgrade Kit Wizard screen.
Required Upgrade Kit	Check box	When this check box is selected, the upgrade kit will be required regardless of previous versions installed. (Component Minimum Version and Component Maximum 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.