Global Deployment Guide > Localizing Global Deployments >

Localizing an Unshipped Language

Topics in this section describe how to localize an unshipped language.

See also About the Localization Process and Localizing Lists of Values and Multilingual Lists of Values.

NOTE:  The process of localizing an unshipped language is considered to be customer configuration. Therefore, such configuration changes are not upgraded as part of the upgrade process described in the Upgrade Guide. Further configuration after an upgrade may be required in order to include new functionality for the localized unshipped language. See also Technical Note 447 on Siebel SupportWeb.

Process of Localizing an Unshipped Language

To localize an unshipped language in your Siebel application, perform the following tasks:

1. Creating Language and Locale Records
2. Creating New Language Subdirectories
3. Creating Application Object Manager Components
4. Creating Virtual Directories on the Web Server
5. Updating the eapps.cfg File on the SWSE
6. Configuring Mobile Web Clients
7. Testing an Unshipped Language
8. Completing Localization for an Unshipped Language