Bookshelf Home | Contents | Index | Search | PDF

Siebel Anywhere Administration Guide > Upgrade Planning and Preliminary Tasks > Preparing Upgrade Kit Contents >

Preparing Contents for a Siebel Executables Upgrade Kit

---

You can use the Siebel Executables component type to deliver Siebel maintenance releases (patches) or additional language packs to Mobile or Dedicated Web Clients.

Siebel maintenance releases consist of a set of language-independent files (called base files) and one or more sets of language-specific files. Base files and language-specific files require different upgrade kits:

Siebel Client Executable upgrade kits are used to distribute base files.
Siebel Client Executable_[language-code] upgrade kits are used to distribute language-specific files.

NOTE:  The base upgrade kit must be installed before language-specific kits are installed. If you wish, you can make the language-specific kits technically dependent on the base kit, so this will be accomplished automatically. For more information see Controlling the Order of Kit Installation. For an overview of the entire process of distributing a Siebel maintenance release, see Distributing a Siebel Maintenance Release (Patch). For tips on distributing language packs alone, see Distributing Additional Language Packs.

The following procedure describes how to prepare upgrade kit contents for base and language-specific portions of a Siebel maintenance release.

To prepare Siebel maintenance release files for inclusion in upgrade kits

On your maintenance release CD, locate and inspect the contents of the \seaw folder.

You should see individual files such as install.exe, data1.cab, and data2.cab. You should also see several subfolders. Some of these are language-independent folders, and some are for specific languages, such as ENU, DEU, and FRA.

Create a network-visible directory to hold base files, such as \\machine\seaw\base.
Copy all language-independent files and subfolders from the CD directory \seaw to the base directory you created in the previous step.
For each language used in your Siebel system, copy the language-specific folder to its own network-visible directory.

For example, you might copy the CD directory \seaw\ENU to \\machine\seaw\ENU.

CAUTION:  Make sure that you use separate directories for base files and for each language's set of language-specific files. The directories for language-specific files should not be subdirectories of the directory that contains base files. Mixing these different file types may prevent proper installation of part of the maintenance release or may result in unnecessarily large upgrade kits.

If you want to change the default installation path that InstallShield will display to subscribers during the installation of the maintenance release, change the appropriate setting in the following siebel.ini files:
Siebel.ini file in the base directory you created in Step 2 of this procedure
Siebel.ini file in each language-specific directory you created in Step 4 of this procedure

For information on siebel.ini file syntax, or for instructions on disabling the InstallShield dialog box for the installation path, see the Packager information in Siebel Web Client Administration Guide. 

If you do not change the siebel.ini file setting, InstallShield will default the client installation path to c:\sea\client, which the subscriber will need to set to the current Siebel client installation location.

For detailed information about defining the upgrade kits for a Siebel maintenance release, see Defining a Siebel Client Executables Upgrade Kit. For an overview of the complete process for distributing a Siebel maintenance release, see Distributing a Siebel Maintenance Release (Patch).

Bookshelf Home | Contents | Index | Search | PDF