About Installing and Deploying with Multiple Languages

Multiple languages may be installed and deployed as part of Siebel Business Applications installation and configuration. This topic outlines three scenarios for deploying the software with more than one language, and identifies some of the requirements for and implications of each approach. This information is presented for your consideration when planning multilingual deployments.

NOTE: It is strongly recommended that the same set of language files be installed on each physical server. Doing so will help ensure maximum compatibility between physical servers, so the system can be reconfigured easily to meet ongoing requirements. Oracle only tests configurations where the same set of language files are installed on each physical server used in a single Siebel Enterprise.

If you include multiple languages with a Siebel Enterprise Server installation, you designate one language as the primary language to be used for server messages. The same primary language is typically also used for the Siebel Database, which cannot be changed after database installation.

When you configure each installed instance of Siebel Server and Siebel Web Server Extension (SWSE), you specify which languages to deploy, from among the installed languages. It is possible to deploy a subset of the installed languages. Which languages you deploy on a given server depends on the uses to which you will put that server.

On each Siebel Server, the set of deployed languages determines which language-specific components such as Application Object Managers (AOMs) are created on that server. It is recommended to deploy all languages installed in the enterprise and optionally to disable AOMs you do not require. See Configuring Siebel Enterprise Server and Related Components.

In addition to software installation tasks, for each installed language besides the primary language, you must perform the following Siebel Database operations, using the Database Configuration Wizard. You perform these tasks after installing the Siebel Database. For more information about these tasks, see Configuring the Siebel Database.

Adding the language (including seed data) to the Siebel Database

Importing the repository into the Siebel Database

Running the MLOV (multilingual LOV) conversion utility

In general, it is recommended to install the latest patch releases before you install the Siebel Database or add languages to the Siebel Database. For information specific to version 8.0.0.x fix pack releases, see the Siebel Maintenance Release Guide on My Oracle Support. See also About Installing Siebel Releases.

If you are localizing a language for which a Siebel Language Pack is not provided, see also the content about localizing an unshipped language in Siebel Global Deployment Guide.

Consider the following scenarios for installing and deploying multiple Siebel Language Packs:

Install and deploy all languages you require once. For customers who are installing and deploying languages shipped with Siebel Business Applications version 8.0, and who do not plan to deploy other languages at a later date. This option is easiest but may not be suitable for phased language deployments.

Install all languages you will require, but deploy some languages later. For customers who are installing and deploying languages shipped with Siebel Business Applications version 8.0, but who plan to deploy some of the installed languages at a later date. This option may be suitable for phased language deployments.

Install and deploy additional languages in an existing deployment. For customers who are installing and deploying languages shipped with Siebel Business Applications version 8.0, and who plan to install and deploy additional languages at a later date. This option may be suitable for some phased language deployments.

You can install languages at any time to meet changing business needs. However, deploying languages is easier if you include them when you first install and configure the Siebel software.

NOTE: This scenario also applies for any Language Packs that are not available with the initial Siebel product release, but that ship subsequently and require a minimum patch release to be installed and deployed (for applicable releases and languages only).