Siebel Anywhere Administration Guide > Defining Upgrade Kits >

Defining a Siebel Repository File Upgrade Kit


This topic provides specific instructions for defining a Siebel Repository File upgrade kit using the Upgrade Kit Wizard. These instructions can be used for the following types of upgrade components, which are always language-specific:

  • Siebel Client Repository File__language-code
  • Siebel Server Repository File__language-code

For either of these component types, two different types of repository file upgrade kits can be created:

  • Standard Repository File Upgrade Kit. Contains a complete SRF repository file.
  • Delta Repository File Upgrade Kit. Contains an incremental SRF file, rather than the complete SRF file. The delta repository file must be created ahead of time, using the Siebel Delta SRF Utility (diffsrf).

NOTE:  The upgrade kit also sets the version of the SRF file in the Siebel Repository File itself. For both Standard Repository File upgrade kits and Delta Repository File upgrade kits, the upgrade kit sets the version in the final Siebel Repository File. When a Delta Repository File upgrade kit is used, the final file that receives the version number is created when the Upgrade Wizard applies the delta file to the base file.

To define a Siebel Repository File upgrade kit

  1. Gather the information and files you will need, as described in Planning and Preparing to Use Siebel Anywhere.
  2. If you are defining a Delta Repository File upgrade kit, then see Roadmap for Creating a Delta Repository File Upgrade Kit.
  3. Start the Upgrade Kit Wizard, as described in Running the Upgrade Kit Wizard.
  4. Use the information you have gathered and the information in Table 20 to respond to the prompts in the Upgrade Kit Wizard.
  5. When you have finished specifying data about the upgrade kit you are defining, click Finish to pass the request to the Upgrade Kit Builder server component and to exit from the Upgrade Kit Wizard.

    A new row for the new upgrade kit appears in the Upgrade Kits list, with Status set to Request Submitted. For more information about the upgrade kit information available in this list and other lists, see Viewing Upgrade Kit Properties.

    After you define your upgrade kit, you must proceed to activate, apply, and distribute it. For more information about these tasks, see Activating, Applying, and Distributing Upgrade Kits.

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

Table 20. Upgrade Kit Wizard Elements for a Siebel Repository File Upgrade Kit
Wizard Element
Element Type
Comments

Upgrade Component

Drop-down list

The 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 a repository file to clients)
  • Siebel Server Repository File__language-code (use when distributing a repository file to servers)

Select File Type

Radio button

Specifies whether the upgrade 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 that 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 that will contain a delta repository file. A delta repository file is an incremental repository file, which supplements the complete repository file. The delta repository file must be created ahead of time, using the Siebel Delta SRF Utility (diffsrf). For more information about creating the delta repository file, see Roadmap for Creating a Delta Repository File Upgrade Kit.

Files to Add

Text field

The Universal Naming Convention (UNC) path and file name of the delta repository file to include in a Delta Repository File upgrade kit. Browsing is available by clicking the Browse button.

Browse

Button

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

UNC Path for SRF file

Text field

The Universal Naming Convention (UNC) path and file name of the standard (complete) SRF file to include in a Standard Repository File upgrade kit.

Minimum Old Version

Read-only text field

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

Maximum Old Version

Read-only text field

The latest component version that can download and install the upgrade kit. This setting is automatically set to NULL for history-independent component types, including repository files, indicating that there are no prerequisite versions required for using the upgrade 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 upgrade 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

The version number that the component being upgraded will have after the upgrade kit is installed. The 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. You can also perform activation 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 dependent on another upgrade kit, then clear this check box. (For example, a repository upgrade kit might be dependent on a Siebel Database Schema upgrade kit.) For more information about working with dependent upgrade kits, see Controlling the Order of Upgrade Kit Installation.

Apply Versions

Check box

This check box is displayed only if you previously selected the Activate Upgrade Kit check box in the Upgrade Kit Wizard.

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. You can also apply versions 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 dependent on another upgrade kit, then clear this check box. For more information about working with dependent upgrade kits, see Controlling the Order of Upgrade Kit Installation.

Required Upgrade Kit

Check box

This check box is displayed only if you previously selected the Apply Versions check box in the Upgrade Kit Wizard.

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 the value of New Version, but this change is not visible in the Upgrade Kit Wizard.)

Upgrade Kit Title

Text field

An identifier for the upgrade kit. The default value is the value of Upgrade Component Name followed by a space and the value of New Version. However, you can modify the title while defining the upgrade kit. After the upgrade kit is defined, this identifier appears in the Name field of the Upgrade Kits list.

Comments

Text field

This field is available for comments about the upgrade kit. Comments entered here are displayed in the Upgrade Kits list.

NOTE:  It is recommended that you keep only one upgrade kit for history-independent components, including repository file upgrade kits. Depending on your preference, you can either delete or deactivate previous upgrade kits for a history-independent component. Deleting an upgrade kit increases available space in the Siebel File System. Deactivating an upgrade kit prevents use of the upgrade kit, while keeping it available in case you need it unexpectedly.

Siebel Anywhere Administration Guide Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.