Siebel Anywhere Administration Guide > Planning and Preparing to Use Siebel Anywhere > Determining Your Upgrade Requirements >

Identifying Software to Be Replaced or Added

Siebel Anywhere can upgrade or distribute many kinds of software. The nature of the software to be upgraded or distributed affects many parts of the process of using Siebel Anywhere:

• Upgrades of existing software. For upgrades of existing software, you must determine the version numbers used by Siebel Anywhere for previous versions of the software being upgraded. You must also decide whether to allow any of those previous versions to remain in use, or whether to require that they be upgraded.
• Distribution of new software. For distribution of new software, you might need to create one or more custom components. Depending on who will use the software, you might also need to create new configurations.

This topic is part of Determining Your Upgrade Requirements.

For language-dependent components, planning the upgrade also includes identifying every end-user language used in your Siebel Business Applications implementation. For example, a CFG file associated with a specific language is a language-dependent component, such as Siebel Sales CFG__ENU for U.S. English, Siebel Sales CFG__DEU for German, or Siebel Sales CFG__JPN for Japanese. Be sure to use the correct end-user language pack (or upgrade component) for each language included in your Siebel Business Applications while creating upgrade kits. For more information regarding the use of different languages, see Example of Global Deployment with Siebel Anywhere.

The number and type of upgrade kits required for your upgrade depend on your subscribers and the components to be upgraded. For example, you might be preparing to upgrade to a new version of your custom Siebel configuration, requiring the distribution of a new SRF file to every Mobile and Developer Web Client user.

Your custom configuration might also need to apply Siebel database schema changes to your Siebel databases and to the local databases of Mobile Web Clients. Siebel database schema changes are not distributed by an upgrade kit to Developer Web Clients. Creating a Siebel Database Schema upgrade kit applies the changes from the logical schema to the physical schema. These changes are visible to Developer Web Clients, without distribution through an upgrade kit, because they connect directly to the Siebel database.

You must create an upgrade kit for each component to be upgraded. In the preceding example, you would need to create one upgrade kit for the Siebel client repository file and a second upgrade kit for the Siebel database schema extensions. Compile a list of the upgrade kits you will need.