Bookshelf v7.5: Defining a Siebel Client Executables Upgrade Kit

This section provides specific instructions for defining a Siebel Client Executables upgrade kit using the Upgrade Kit Wizard. Instructions in this section apply to the following two component types:

Each of these component types needs its own kit. For example, if you want to install a Siebel maintenance release on a Siebel system that uses both English and German, you would need at least three upgrade kits, one each for Siebel Client Executables, Siebel Client Executables_ENU, and Siebel Client Executables_DEU. The base kit must be installed before the language-specific kits. For instructions on enforcing this by making the language-specific kits dependent on the base kit, see Controlling the Order of Kit Installation. For a general overview of the process of deploying a Siebel maintenance release, see Distributing a Siebel Maintenance Release (Patch).

The following procedure describes how to define either a Siebel Client Executables kit for the base component, or a Siebel Client Executables_[language-code] kit for a language-specific component.

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

Table 18. Upgrade Kit Wizard Elements for a Siebel Client Executables Upgrade Kit
Wizard Element	Element Type	Comments
Upgrade Component	Drop-down list	Name of the component the upgrade kit will install or upgrade: For the language-independent or base part of a Siebel maintenance release (patch) for clients, select Siebel Client Executable. For the language-specific part of a Siebel maintenance release (patch) for clients, select Siebel Client Executable_[language-code], such as Siebel Client Executable_ENU.
UNC Path for Master Installation	Text field	Universal Naming Convention (UNC) path to the directory that contains the files for the upgrade. The path should identify a network-accessible location. For the base component of a Siebel maintenance release (patch), a typical path would be \\machine\seaw\base. For a language-specific component of a Siebel maintenance release (patch), a typical path would be \\machine\seaw\ENU. For a full release in which Siebel Packager has been used to create an installation package, you must choose the directory where the package was created.
Destination Directory	Text field	Specifies where the files of the upgrade kit are to be placed on the client machine.
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. If you are defining this kit for a Siebel Client maintenance release, be sure to clear this check box.
Uninstall previous Siebel version	Check box	When this check box is selected, the Upgrade Wizard will automatically uninstall all existing Siebel applications before proceeding with installation of the upgrade. If you are creating a kit for a Siebel Maintenance Release (patch), be sure to clear this check box. If you are creating a kit for a complete Siebel Release (such as a kit to upgrade release 7.5 client executables to release 7.7), select this check box.
File to execute	Read-only text field	Specifies one file in the upgrade kit to be executed as part of installation of the kit. Automatically set to install.exe for this component type, indicating that install.exe will be run from the directory identified in UNC Path for Master Installation.
Enter command line arguments	Text field	Specifies any command line arguments to use when running the install.exe file. If you are defining this kit for a Siebel Client maintenance release, do not change the default command line arguments supplied in this field.
Major Version	Text field	Enter a value from the first part of the release number. For example, for maintenance release version 7.5.2.211, set Major Version to 7.
Minor Version	Text field	Enter a value from the second part of the release number. For example, for maintenance release version 7.5.2.211, set Minor Version to 5.
Maintenance Version	Text field	Enter a value from the third part of the release number. For example, for maintenance release version 7.5.2.211, set Maintenance Version to 2.
Patch Version	Text field	Enter a value from the fourth part of the release number. For example, for maintenance release version 7.5.2.211, set Patch Version to 211.
Vertical Code	Drop-down list	If you are using industry-specific Siebel applications, such as Siebel Consumer Sector or Siebel Financial Services, choose SIA from the drop-down list. For all other Siebel eBusiness Applications, leave the field blank.
Activate Upgrade Kit	Check box	It is recommended that you clear this check box for all Siebel Client Executables upgrade kits. If 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	It is recommended that you clear this check box for all Siebel Client Executables upgrade kits. 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.

NOTE: To avoid unnecessary download operations, it is recommended that you keep only one upgrade kit for history-independent components, including Siebel Client Executables kits. Depending on your preference, you can either delete or inactivate previous kits for a history-independent component. Deleting a kit increases available space in the Siebel File System. Inactivating a kit prevents use of the kit, while keeping it available in case you need it unexpectedly.