Installing in Arabic, Hebrew, and Turkish

You cannot perform the installation on machines whose locale is Arabic Hebrew, or Turkish. This limitation applies to both the WebSphere® Business Monitor server component and dashboards component.

For those languages, you must first install WebSphere Business Monitor components on a machine with English locale, and after you complete the installation, you can change the machine language to the required locale (Turkish, Hebrew, or Arabic). You must also go to the WebSphere Portal administration. Select Administration > Portal settings > Global settings, and change the WebSphere Portal default language to the same preferred language. After you change the WebSphere Portal language, you must restart the WebSphere Portal.

Database creation consideration

You need to consider the following information, regarding database creation, based on the fact that you need to run the launchpad on English locale to install WebSphere Business Monitor on machines with Arabic, Hebrew, or Turkish locales.

When the launchpad runs the scripts to create the databases, it sets the territory code based on the current locale. The territory code affects string comparisons and date formats. Therefore, if the you run the launchpad in an English locale, the territory code will be "US".

Although the launchpad must run on English locale, after installation you can use both Monitor Server and Dashboard Client on Arabic, Hebrew, or Turkish locale. Thus, you will need to create the Monitor databases using the territory code for the preferred locale (Arabic, Hebrew, or Turkish). To change the territory code to represent Arabic, Hebrew, or Turkish locale, after the creation of database, complete the following steps. Make sure the locale is English.

  1. Go to a DB2 command prompt and execute this command for each Monitor database that will be created on the current machine:

    DB2 create database <db_name> using codeset UTF-8 territory <territory_code>

    Where: <db_name> is the database name, such as State, Runtime, etc.

    <territory_code> must be "TR" for Turkish locale, "AA" for Arabic locale and "IL" for Hebrew locale.

  2. Go back to the launchpad and create each Monitor database. In the database creation log files, an error will be raised from the DB2 "create database" command because the database already exists. Ignore this error. The tables within the database will be created successfully.

Copyright IBM Corporation 2005, 2006. All Rights Reserved.