Implementing Siebel eBusiness Applications on DB2 UDB for OS/390 and z/OS > Siebel Repository Import, Export, and Postinstallation Tasks > Postinstallation Tasks >

Installing Multilingual Seed Data


If your organization deploys internationally and, therefore, requires data to be in multiple languages, you must install multilingual seed data (for example, lists of views, responsibilities, or system preferences). To do this, you add new language packs to your database after you have installed the base language for your database server. This populates the List of Values (LOV) with seed data in the new language.

Only after you successfully install seed data in your base language, can you add seed data in other languages to your database. Adding this seed data also adds new LOV data in the new language.

CAUTION:  You cannot add secondary languages to the Siebel database for an Enterprise Server unless you have already installed them on the associated Siebel Server.

To install multilingual seed data under Windows

  1. Follow the instructions under Siebel Database Server Software Installation, using the CD for the new language that you want to install.
  2. In the Existing Installations Found screen, select the installation to which you want to add the language.
  3. When installation is complete, launch the Database Server Configuration Utility.
  4. When the Select Installation Operation screen appears (Step 7), select Add a language to an existing Siebel Database, and then click Next.
  5. NOTE:  To add seed data in a new language to your database, you must have already imported your repository in its base language.

    The Base Language screen appears and displays the languages you have installed for your Siebel Database.

  6. In the Base Language screen, specify which of the languages you installed is the one in which you want to primarily run your database. (This is known as your base language.)
  7. To continue, click Next.

    NOTE:  The Language Selection screen appears only if you have installed the files for multiple Siebel Language Packs. Installation of multiple Language Packs can occur either during your initial installation of Siebel 7 or at a later time.

  8. In the Language Selection screen, specify the new language you are adding for this database.
  9. To continue, click Next.

    The ODBC Data Source Name screen appears.

  10. Respond to the remaining prompts as you did when you originally completed the procedure, Installing the Siebel Schema, until the Repository Name screen appears.
  11. Type the name of your Siebel Repository or accept the displayed default name.
  12. To continue, click Next.

  13. In the Configuration Parameter Review screen, review the configuration values you entered on the previous configuration screens:
  14. To apply the configuration now, press "OK".
    To apply the configuration later, press "Cancel".
    The command line to apply the configuration later is
    C:\sea704\siebsrvr\bin\siebupg.exe /m master_install_lang.ucf

    NOTE:  The last line in the prompt is generated dynamically based on the location of your Siebel Server installation.

    If a program or system error occurs and you need to rerun the Siebel Upgrade Wizard, you can do so, starting at the point at which the wizard failed, by navigating to \siebsrvr\bin and entering:

    siebupg.exe /m master_install_lang.ucf

    The DB Server Configuration Utility displays the items to be executed or imported.

  15. To begin, click OK.
  16. A window appears, displaying information about installation activities. Afterwards, a message appears when the installation is complete.

    To verify that the installation was successful, review the log files. See Reviewing the Log Files for Repository Import.

TIP:  Locate the file master_install_lang.ucf in the binary subdirectory of your Siebel Server installation directory and print it out, so that you have a record of the values you entered.

  1. When you have finished configuration using the DB Server Configuration Utility, you must enable the multilingual list of values (MLOV) capability within Siebel eBusiness Applications. For information on how to do this, see Global Deployment Guide.
  2. After you enable MLOV capability as described in Global Deployment Guide, proceed to Importing a New Language to Your Repository.

To install multilingual seed data under UNIX

  1. Follow the UNIX instructions under Siebel Database Server Software Installation, using the CD for the new language that you want to install.
  2. Follow the instructions for UNIX under Performing a Standard Installation and when prompted for the installation operation (Step 7), enter 2 to Add New Language to an Existing Database.
  3. At the Language Selection prompt, specify which of the displayed languages you are adding on top of your base language for this database.
  4. At the Base Language prompt, specify which language you want as your base language.
  5. Respond to the remaining prompts as you did when you originally completed the procedure for Installing the Siebel Schema whether you chose standard or custom installation.
  6. When you are prompted for the repository name, accept the default (Siebel Repository) or enter another name.
  7. Review the values for accuracy.
  8. To begin, click OK.
  9. A message appears when the installation is complete.

    To verify that the installation was successful, review the log files. See Reviewing the Log Files for Repository Import.

TIP:  Locate the file master_install_lang.ucf in the binary subdirectory of your Siebel Server installation directory and print it out, so that you have a record of the values you entered.

  1. When you have finished configuration using the Configuration Wizard, you must enable the multilingual list of values (MLOV) capability within Siebel eBusiness Applications. For information on how to do this, see Global Deployment Guide.
  2. After you enable MLOV capability as described in Global Deployment Guide, proceed to Importing a New Language to Your Repository.

 Implementing Siebel eBusiness Applications on DB2 UDB for OS/390 and z/OS 
 Published: 18 April 2003