Bookshelf v7.5: Distributing a Siebel Maintenance Release (Patch)

Siebel Anywhere Administration Guide > Supplementary Information for Specific Upgrade Types >

Distributing a Siebel Maintenance Release (Patch)

This section provides an overview of the process of deploying a Siebel maintenance release (patch), including links to more specific instructions.

CAUTION: Do not use Packager for Siebel maintenance releases. Packager is designed for use with full releases. It does not include the necessary functionality to install a Siebel release that depends on the existence of a previous release.

NOTE: Only Mobile and Dedicated Web Clients can use Siebel Anywhere to download the kits needed for a Siebel maintenance release. For other types of clients, such as Siebel Tools clients, users can only receive notification and then manually apply the patch. For information about applying matches manually, see the Maintenance Release Guide for the patch, which is available on Siebel SupportWeb.

The process of distributing a Siebel maintenance release consists of the following steps:

Determine your upgrade requirements. For instructions concerning this step, see Determining Upgrade Requirements.

Prepare any needed infrastructure elements, such as configurations. For instructions concerning this step, see Creating Needed Infrastructure Elements.

Prepare Siebel maintenance release files for inclusion in upgrade kits. For instructions concerning this step, see Preparing Contents for a Siebel Executables Upgrade Kit.

NOTE: In this step, it is important to keep the language-independent base files and the files specific to each language in separate directories.

Define the following upgrade kits:

NOTE: Although the following kits can be created in any order, it is important to wait for the status of each kit to become Pending before defining the next kit. Press ALT+ENTER to refresh the view. You may need to refresh the view several times before you will see the Status change.

Define an upgrade kit for the language-independent (base) portion of the maintenance release. For instructions concerning this step, see Defining a Siebel Client Executables Upgrade Kit.

For each language that you use in your Siebel implementation, define an upgrade kit for the language-specific part of the maintenance release. For instructions concerning this step, see Defining a Siebel Client Executables Upgrade Kit.

NOTE: In Step 4, you define each upgrade kit to execute a different install.exe file.

Make each language-specific upgrade kit dependent upon the base upgrade kit. For instructions concerning this step, see Controlling the Order of Kit Installation.

Activate each base and language-specific kit you created. For instructions concerning this step, see Activating an Upgrade Kit.

Apply each base and language-specific kit you created. For instructions concerning this step, see Applying an Upgrade Kit.

Distribute the base and language-specific kits to a test configuration. For instructions concerning this step, see Distributing Upgrade Kits.

Test the upgrade kits by retrieving and installing them as both local and remote members of the test configuration, and by running the software that has been upgraded. For instructions concerning this step, see Retrieving, Installing, and Testing Upgrade Kits.

After each base and language-specific kit is operating correctly for test configuration members, distribute the kit to one or more additional configurations, for general use.