|Bookshelf Home | Contents | Index | PDF|
For language-dependent components, planning the upgrade also includes identifying every end-user language used in your Siebel implementation. For example, a CFG file associated with a specific language is a language-dependent component, such as Siebel Sales CFG_ENU for 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 may 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 may also need to apply database schema changes to your Siebel databases and to the local databases of Mobile Web Clients. Database schema changes are not distributed by a kit to Developer Web Clients. Creating a database schema kit applies the changes from the logical schema to the physical schema. These changes are visible to Developer Web Clients, without distribution through a kit, because they connect directly to the Siebel Server 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 database schema extensions.
|Siebel Anywhere Administration Guide|