Bookshelf Home | Contents | Index | PDF     

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 be used for the unshipped language.

If you localize the user interface and optionally MLOV values or other seed data into Polish (PLK), you would set the Language Code parameter to PLK. However, because DLLs located in language-specific subdirectories are not provided in Polish for Siebel Business Applications and cannot be localized into Polish, you would set the OM - Resource Language Code parameter to DEU or ENU in order to use DLLs 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. The directory names you use must correspond to the language code you specified in Creating Language and Locale Records.

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

Table 11. Language Placeholders Used in This Guide
Placeholder
Definition

XXX

The unshipped language you are localizing—for example, PLK (Polish).

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 to the unshipped language XXX. Sometimes you may 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 you are localizing, rather than copy them from the base language.

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

  1. On the Siebel Server machine, create a language subdirectory XXX under SIEBSRVR_ROOT\objects, where XXX is the unshipped language you are localizing, such as PLK for Polish.
  2. Copy the contents of SIEBSRVR_ROOT\objects\YYY into this directory, where YYY is the shipped base Siebel language.

    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 configuration files from SIEBSRVR_ROOT\bin\YYY into SIEBSRVR_ROOT\bin\XXX. The configuration files (CFG files such as uagent.cfg for Siebel Call Center) will be used by the Application Object Managers you will create for language XXX.

    NOTE:  In order to run programs like genbscript, you must also copy all binary files to the target directory, along with the configuration files. Because binary files may be updated through patch installation, you must also do this after each installation of a patch release. For more information about genbscript, see Configuring Siebel Business Applications. For more information about installing patch releases, see the Siebel Maintenance Release Guide on Siebel SupportWeb.

  4. For Siebel Industry Applications (SIA), create a new language subdirectory XXXSIA (such as PLKSIA) under SIEBSRVR_ROOT\bin. Copy the contents of YYYSIA (such as DEUSIA or ENUSIA) into this directory.

    NOTE:  If you apply a patch release to the Siebel Server after completing localization, recopy files from YYYSIA to XXXSIA 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\reports. Copy the contents of SIEBSRVR_ROOT\reports\YYY into this directory.
  7. Create a new language subdirectory XXX under SIEBSRVR_ROOT\webmaster. Copy the contents of SIEBSRVR_ROOT\webmaster\YYY into this directory.
  8. Create a new language subdirectory XXX under SIEBSRVR_ROOT\webmaster\files. Copy the contents of SIEBSRVR_ROOT\webmaster\files\YYY into this directory.
  9. Create a new language subdirectory XXX under SIEBSRVR_ROOT\webmaster\help. Copy the contents of SIEBSRVR_ROOT\webmaster\help\YYY into this directory.
  10. Create a new language subdirectory XXX under SIEBSRVR_ROOT\webmaster\images. Copy the contents of SIEBSRVR_ROOT\webmaster\images\YYY into this directory.
  11. 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.
  12. In SIEBSRVR_ROOT\webmaster\siebel_build\scripts\XXX, rename the file swemessages_yyy.js to be swemessages_xxx.js, such as swemessages_plk.js for Polish.

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

To create language subdirectories for an unshipped language on the SWSE

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

    NOTE:  Each time the Web server is restarted, files and subdirectories are automatically copied from the webmaster folder on the Siebel Server to the public folder on the SWSE. For more information, see the Siebel Installation Guide for the operating system you are using.

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

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

    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 configuration files only 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.
  4. For Siebel Industry Applications (SIA), create a new language subdirectory XXXSIA (such as PLKSIA) under SIEBEL_CLIENT_ROOT\bin. Copy the contents of YYYSIA (such as DEUSIA or ENUSIA) into this directory.

    NOTE:  If you apply a patch release to the Mobile Web Client after completing localization, 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 SIEBSRVR_ROOT\reports. Copy the contents of SIEBSRVR_ROOT\reports\YYY into this directory.
  7. Create a new language subdirectory XXX under SIEBEL_CLIENT_ROOT\public. Copy the contents of SIEBEL_CLIENT_ROOT\public\YYY into this directory.
  8. 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_plk.js for Polish.

    NOTE:  If you apply a patch release to the Mobile Web Client after completing localization, copy any newly created folder corresponding to Siebel_Build above from 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.

  
Siebel Global Deployment Guide Copyright © 2007, Oracle. All rights reserved.