Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Siebel Global Deployment Guide > Overview of Global Deployments > Global Deployment Terminology > LanguageThis topic is part of Global Deployment Terminology. The language for a Siebel application can mean multiple things, and might involve different system or application elements. These elements are independent from the language of the data that the user enters in the Siebel database. You must install seed data according to how you want to use languages in the Siebel applications. Primary Language, Active Language, and Resource LanguageThe term language has the following major meanings with respect to Siebel Business Applications:
Languages and Siebel Installations and UpgradesInstalling Siebel Language Packs on the Siebel Server (or on other Siebel components) installs the language-specific run-time environment: Siebel repository (SRF) files, resource libraries such as DLL files, configuration (CFG) files, error messages, help files, and so on. In general, you install the same languages on all of the components in your Siebel Enterprise. For more information, see Scenarios for Installing and Deploying Siebel Languages. When you install the Siebel database for a new installation, language-specific seed data is added for the primary language only. For multilingual deployments, you must add seed data for additional languages separately after your initial Siebel database installation. When you upgrade the Siebel database from a prior Siebel version, all of the existing languages are upgraded at the same time. For more information, see Siebel Database Upgrade Guide. The languages allowed in data are constrained only by the character encoding of the database platform. For example, although a user might be using a U.S. English version of a Siebel application with a Western European code page database, the user can enter or view contact data in French, because all French characters are representable in the Western European code page. With a Unicode code page, and appropriate fonts locally installed, languages using dissimilar scripts, such as French and Japanese, can be used together. Language CodesEach language code used by Siebel Business Applications uses a three-letter code, such as ENU for U.S. English, FRA for French, THA for Thai, and so on. Using language codes with only two characters does not work and is not supported. NOTE: For a list of the languages supported by Siebel Business Applications, and their language codes, see Article ID 1513102.1 (for version 8.1.1.x) or Article ID 1524342.1 (for version 8.2.2.x) on My Oracle Support. They are also listed in Table 9. Special requirements apply when you localize an unshipped language, as noted in Localizing an Unshipped Language. Languages and Application Development and DeploymentFor application development using Siebel Tools, you set the language mode to work with object definitions for a particular language. The language of an SRF file is determined by the language mode in effect when the SRF file was compiled. For information about the language mode in Siebel Tools and how to set it, see Using Siebel Tools. Although one Application Object Manager component can support only one language and one SRF file, multiple Application Object Managers can run at the same time on the same Siebel Server, each configured for a different language, and therefore using a different SRF file. Additional InformationThe following contain more information about language deployment for Siebel applications:
|
![]() |
![]() ![]() |
Siebel Global Deployment Guide | Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |