Siebel Global Deployment Guide > Configuring Global Deployments >

About Parameters for Language and Locale

This topic describes the parameters that can be set on the Application Object Manager in order to specify language, resource language, and locale.

On the Siebel Mobile Web Client, equivalent parameters may be set in the application configuration file (such as uagent.cfg for Siebel Call Center).

NOTE:  If you are localizing an unshipped language, see also Localizing an Unshipped Language. In particular, for scenarios for setting the language parameters, see Creating Language and Locale Records and Creating Application Object Manager Components.

Language Code

The Language Code parameter (alias Lang) determines the language used for multilingual lists of values (MLOVs) and other application seed data. This parameter also determines which language-specific directory from the product installation will be used for accessing the SRF file. The language of application user interface labels is determined by the language for the SRF file. This language was determined by the Siebel Tools language mode in effect when the SRF file was compiled.

For each language you install and deploy, Application Object Manager components are created which are already configured with Language Code set to this language. In general, you do not need to change the value of the Language Code parameter for these components.

Special requirements apply when you localize an unshipped language. For details, see Localizing an Unshipped Language.

The Application Repository File parameter (alias CFGRepositoryFile), set for the Application Object Manager, specifies the name of the SRF file. Where appropriate, this parameter can optionally specify the absolute path to the SRF file, in order to use the SRF file in a different language directory—such as to display the user interface in a different language than that specified by Language Code.

Unless the OM - Resource Language Code parameter is also set (to a different language), the Language Code parameter also determines which language-specific directories will be used during runtime operation for resource libraries such as DLLs. These resource libraries determine the language in which system and error messages display and the language in which server log file messages are written.

Each language has its own three-letter code identifier—for example, ENU identifies U.S. English. Languages supported for Siebel Business Applications are identified in Siebel System Requirements and Supported Platforms on Siebel SupportWeb. See also Table 8.

NOTE:  On the Siebel Mobile Web Client, the equivalent parameter is the Language parameter in the [Siebel] section of the configuration file. For each language you install, language-specific directories are created containing the configuration files, in which Language is already set. In general, you do not need to change the value of the Language parameter. Special requirements apply when you localize an unshipped language. For details, see Localizing an Unshipped Language.

The setting of the Preferred Language field in the Contacts screen overrides the value of the Language Code parameter for determining the language for multilingual lists of values (MLOVs). This setting is stored in S_CONTACT.PREF_LANG_ID in the Siebel Database. This field does not affect Mobile or Developer Web Client users.

See also Localizing Lists of Values and Multilingual Lists of Values.

See also the description for OM - Resource Language Code and see About the Active Language.

For more information about the effect of the language mode in Siebel Tools and about how to set it, see Using Siebel Tools.

OM - Resource Language Code

The OM - Resource Language Code parameter (alias ResourceLanguage) can optionally be set to a different language than the Language Code parameter in order to specify the resource language.

The resource language determines which language-specific directories from the product installation will be used during runtime operation for resource libraries such as DLLs. These resource libraries determine the language in which system and error messages display and the language in which server log file messages are written.

DLLs are provided for all languages shipped with Siebel Business Applications. These DLLs cannot be localized into any other unshipped languages.

For some multilingual deployments, it may be useful, or necessary, to set the resource language to a different value than the Language Code parameter. For example, you may want all global users to view MLOV and other seed data in the language determined by Language Code. However, you may choose to set the resource language to a single language familiar to your administrators.

Where Language Code is set to an unshipped language, you must use the DLLs for a language provided for Siebel Business Applications. In this case, you can set OM - Resource Language Code to specify which language's DLLs to use. For example, where Language Code is set to the unshipped language PLK (Polish), you might set OM - Resource Language to DEU (German). For details, see Localizing an Unshipped Language.

NOTE:  On the Siebel Mobile Web Client, the equivalent parameter is the ResourceLanguage parameter in the [Siebel] section of the configuration file.

See also the description for Language Code and see About the Active Language.

Locale Code

The Locale Code parameter (alias LocaleCode) specifies the locale associated with this Application Object Manager (AOM) component. This setting is used by the Siebel Web Clients for this AOM.

The Locale Code setting is a three-letter locale code. A locale is a set of rules guiding how common data is displayed to the user or is received from the user. Siebel Business Applications support formatting of data, such as dates, time, numbers, and currency, based on locale settings.

Locales are administered using the Locale Administration view.

For each language-specific AOM component on a Siebel Server, the Locale Code is set to a locale that may be appropriate for users for that language. If you need to support multiple locales for the same language, then you can use either of the following approaches to deploy your AOMs:

• On different servers, configure and run different locale-specific AOMs for this language on different Siebel Servers. For example, an FRA AOM would be running in France with a French locale, while another FRA AOM would be running in Canada with a French Canadian locale.
• On the same server, create, configure and run different AOMs that are specific to both this language and a particular locale. For example, one FRA AOM running in France would have a French locale, while another FRA AOM on the same Siebel Server in France would have a French Canadian locale.

If the Locale Code parameter is not set, then the AOM and the Siebel Web Clients use the locale defined in the operating system on the Siebel Server machine. On Windows, this setting is defined in Regional and Language Options in the Control Panel.

NOTE:  On the Siebel Mobile or Developer Web Client, the locale is always determined by the settings defined in Regional and Language Options in the Control Panel.

Additional Information About Setting Up and Administering Locales

During installation, you need to set locales for your Siebel Web Clients, Siebel Servers, and database. After installation, you can modify the Siebel Server locale or add additional locales. Table 5 shows where you can find detailed information on performing these procedures.