Siebel Global Deployment Guide > Localizing Global Deployments > Localizing an Unshipped Language >

Creating New Language Subdirectories


This topic is part of Localizing an Unshipped Language.

When you are localizing an unshipped language, you typically create new language subdirectories to use for the unshipped language.

If you localize the user interface and optionally MLOV values or other seed data into Norwegian (NOR), then you would set the Language Code parameter to NOR. However, resource library files located in language-specific subdirectories are not provided in Norwegian for Siebel Business Applications and cannot be localized into Norwegian. For this reason, you would set the OM - Resource Language Code parameter to DEU or ENU in order to use resource libraries from subdirectories for DEU or ENU. For more information, see About Parameters for Language and Locale.

You create language subdirectories on the Siebel Server, on the Siebel Web Server Extension (SWSE), and on the Siebel Mobile Web Client, as described in the following tasks. The directory names that you use must correspond to the language code that you specified in Creating Language and Locale Records.

NOTE:  Follow-up tasks might be required after performing the tasks in this section. For example, if the original configuration files or SRF files that you copied are updated later, you might have to recopy the original files or make similar updates in copied files such as configuration files. Also, after performing a migration installation (installing a Siebel Fix Pack release as a patch installation for the Siebel Enterprise Server or Siebel Web Server Extension), verify that all of the directories and files for your unshipped languages migrated correctly. For more information, see the Siebel Installation Guide for the operating system you are using.

Table 12 explains the language placeholders that are referred to in the procedures in this task and in the remaining tasks listed in Process of Localizing an Unshipped Language.

Table 12. Language Placeholders Used in This Guide
Placeholder
Definition

XXX

The unshipped language that you are localizing, for example, NOR (Norwegian).

YYY

The base language of the application: for example, DEU (German) or ENU (U.S. English). You are copying files from language directories for the shipped language YYY into new directories for the unshipped language XXX. Sometimes you might also update the names of copied files to include XXX instead of YYY.

NOTE:  Alternatively, you can copy files from some other language (shipped for Siebel Business Applications) to the unshipped language that you are localizing, instead of copying them from the base language. For example, perhaps ENU (U.S. English) is the base language, but you choose to copy files from DEU directories instead of copying from ENU directories.

Related Books

Siebel Installation Guide for the operating system you are using

Creating Language Subdirectories for an Unshipped Language on the Siebel Server

Use the following procedure to create language subdirectories for an unshipped language on the Siebel Server.

To create language subdirectories for an unshipped language on the Siebel Server

  1. On the Siebel Server computer, create a language subdirectory XXX under SIEBSRVR_ROOT\objects, where XXX is the unshipped language that you are localizing, such as NOR for Norwegian.
  2. Copy the contents of SIEBSRVR_ROOT\objects\YYY into this directory, where YYY is the shipped base Siebel language, such as DEU for German.

    NOTE:  Because you have copied the SRF file for another language, the Siebel application user interface will display in language YYY unless or until you compile a new SRF for the unshipped language XXX.

  3. Create a new language subdirectory XXX under SIEBSRVR_ROOT\bin. Copy the configuration files from SIEBSRVR_ROOT\bin\YYY into SIEBSRVR_ROOT\bin\XXX. The configuration files (that is, the CFG files such as uagent.cfg for Siebel Call Center) will be used by the Application Object Managers that you will create for language XXX.

    NOTE:  In order to run certain Siebel programs, including genbscript, you must also copy all of the binary files (that is, the library files in the bin\YYY directory) to the target directory, along with the configuration files. After completing the localization tasks, you must recopy the files from the bin\YYY directory after each time that you install a patch release for the Siebel Server, to keep your localized product up to date. For more information about genbscript, see Configuring Siebel Business Applications. For more information about installing patch releases, see the Siebel Installation Guide for the operating system you are using.

  4. Create a new language subdirectory XXXSIA (such as NORSIA) under SIEBSRVR_ROOT\bin. Copy the contents of YYYSIA (such as DEUSIA or ENUSIA) into this directory.

    NOTE:  After completing localization, you must recopy the files from YYYSIA to XXXSIA after each time that you install a patch release for the Siebel Server, to keep your localized product up to date.

  5. Create a new language subdirectory XXX under SIEBSRVR_ROOT\msgtmpl. Copy the contents of SIEBSRVR_ROOT\msgtmpl\YYY into this directory.
  6. Create a new language subdirectory XXX under SIEBSRVR_ROOT\webmaster. Copy the contents of SIEBSRVR_ROOT\webmaster\YYY into this directory.
  7. Create a new language subdirectory XXX under SIEBSRVR_ROOT\webmaster\files. Copy the contents of SIEBSRVR_ROOT\webmaster\files\YYY into this directory.
  8. Create a new language subdirectory XXX under SIEBSRVR_ROOT\webmaster\help. Copy the contents of SIEBSRVR_ROOT\webmaster\help\YYY into this directory.
  9. Create a new language subdirectory XXX under SIEBSRVR_ROOT\webmaster\images. Copy the contents of SIEBSRVR_ROOT\webmaster\images\YYY into this directory.
  10. Create a new language subdirectory XXX under SIEBSRVR_ROOT\webmaster\siebel_build\scripts. Copy the contents of SIEBSRVR_ROOT\webmaster\siebel_build\scripts\YYY into this directory.
  11. In SIEBSRVR_ROOT\webmaster\siebel_build\scripts\XXX, rename the file swemessages_yyy.js to be swemessages_xxx.js, such as swemessages_nor.js for Norwegian.

    NOTE:  If you install a patch release for the Siebel Server after completing localization, then recopy the file swemessages_yyy.js from the YYY directory to XXX (and rename the file again, as described) to keep your localized product up to date.

  12. Similar to what you did in Step 11, identify any language-specific files that you copied and rename them in their new locations to refer to language XXX instead of language YYY.
Related Books

Siebel Installation Guide for the operating system you are using

Configuring Siebel Business Applications

Version 8.1.1.x Siebel Maintenance Release Guide on My Oracle Support (Article ID 880452.1)

Version 8.2.2.x Siebel Maintenance Release Guide on My Oracle Support (Article ID 1441523.1)

Creating Language Subdirectories for an Unshipped Language on the SWSE

Use the following procedure to create language subdirectories for an unshipped language on the SWSE.

To create language subdirectories for an unshipped language on the SWSE

  1. On the Siebel Web Server Extension (SWSE) computer, create a language subdirectory XXX under SWSE_ROOT\public, where XXX is the unshipped language that you are localizing, such as NOR for Norwegian.
  2. Copy the contents of SWSE_ROOT\public\YYY into this directory, where YYY is the shipped base Siebel language, such as DEU for German.

    NOTE:  Each time the Web server is restarted, files and subdirectories are automatically copied from the webmaster directory on the Siebel Server to the public directory on the SWSE. You can also update files manually without restarting the Web server.

Related Books

Siebel Installation Guide for the operating system you are using

Siebel Security Guide

Creating Language Subdirectories for an Unshipped Language on the Siebel Mobile Web Client

Use the following procedure to create language subdirectories for an unshipped language on the Siebel Mobile Web Client.

To create language subdirectories for an unshipped language on a Siebel Mobile Web Client

  1. On a Siebel Mobile Web Client computer, create a language subdirectory XXX under SIEBEL_CLIENT_ROOT\objects, where XXX is the unshipped language that you are localizing, such as NOR for Norwegian.
  2. Copy the contents of SIEBEL_CLIENT_ROOT\objects\YYY into this directory, where YYY is the shipped base Siebel language, such as DEU for German.

    NOTE:  Because you have copied the SRF file for another language, the Siebel application user interface will display data in language YYY unless or until you compile a new SRF for unshipped language XXX.

  3. Create a new language subdirectory XXX under SIEBEL_CLIENT_ROOT\bin. Copy the configuration files from SIEBEL_CLIENT_ROOT\bin\YYY into this directory. The configuration files (CFG files such as uagent.cfg for Siebel Call Center) will be used by the application for language XXX.

    NOTE:  In order to run certain Siebel programs, including Siebel Handheld Companion Synchronization, you must also copy all of the binary files (that is, the library files in the bin\YYY directory) to the target directory, along with the configuration files. After completing the localization tasks, you must recopy the files from the bin\YYY directory after each time that you install a patch release for the Siebel client, to keep your localized product up to date.

  4. Create a new language subdirectory XXXSIA (such as NORSIA) under SIEBEL_CLIENT_ROOT\bin. Copy the contents of YYYSIA (such as DEUSIA or ENUSIA) into this directory.

    NOTE:  If you install a patch release for the Mobile Web Client after completing localization, then recopy files from YYYSIA to XXXSIA to keep your localized product up to date.

  5. Create a new language subdirectory XXX under SIEBEL_CLIENT_ROOT\msgtmpl. Copy the contents of SIEBEL_CLIENT_ROOT\msgtmpl\YYY into this directory.
  6. Create a new language subdirectory XXX under SIEBEL_CLIENT_ROOT\public. Copy the contents of SIEBEL_CLIENT_ROOT\public\YYY into this directory.
  7. In SIEBEL_CLIENT_ROOT\public\XXX\Siebel_Build\scripts (where Siebel_Build is a build number), rename the file swemessages_yyy.js to be swemessages_xxx.js, such as swemessages_nor.js for Norwegian.

    NOTE:  If you install a patch release for the Mobile Web Client after completing localization, then copy any newly created directory corresponding to Siebel_Build from the directory YYY to XXX, to keep your localized product up to date. Also rename the file swemessages_yyy.js to be swemessages_xxx.js, as you did earlier.

  8. Similar to what you did in Step 7, identify any language-specific files that you copied and rename them in their new locations to refer to language XXX instead of language YYY.
Related Books

Siebel Installation Guide for the operating system you are using

Siebel Global Deployment Guide Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.