Work in non-English locales

The OMi user interface can be viewed in the following languages in your web browser:

The following are languages in which OMi can operate but the user interface of only Run-time Service Model (RTSM)-related pages are presented in the language:

Use the language preference option in your browser to select how to view OMi. The language preference chosen affects only your local machine (the client machine) and not the OMi machine or any other user accessing the same OMi machine.

1. Install the appropriate language's fonts on your local machine if they are not yet installed. If you select a language in your web browser whose fonts have not been installed, OMi displays the characters as squares.

2. If you are logged into OMi, you must log out. Click Log Out at the top of the OMi window.

   Close every open browser window or, alternatively, clear the cache (if OMi is running on Internet Explorer).

3. If OMi is running on Internet Explorer, configure the web browser on your local machine to select the language in which you want to view OMi (Tools > Internet Options).

   1. Click the Languages button and in the Language Preference dialog box, highlight the language in which you want to view OMi.

   2. If the language you want is not listed in the dialog box, click Add to display the list of languages. Select the language you want to add and click OK.

   3. Click Move Up to move the selected language to the first row.

   4. Click OK to save the settings.

   5. Open the OMi log-in window.

   6. From the Internet Explorer menu, select View > Refresh. OMi immediately refreshes and the user interface is displayed in the selected language.

      Note For details on viewing Internet Explorer, see How to View Web Pages That Are Written in a Different Language.

4. If OMi is being viewed on Firefox, configure the web browser on your local machine as follows:

   1. Select Tools > Options > Advanced. Click Edit Languages. The Language dialog box opens.

   2. Highlight the language in which you want to view OMi.

   If the language you want is not listed in the dialog box, expand the Select language to add... list, select the language, and click Add.

   3. Click Move Up to move the selected language to the first row.

   4. Click OK to save the settings. Click OK to close the Language dialog box.

1. Verify that you correctly followed the instructions for installing the JRE on a non-Western Windows system. See the Oracle web site for details (http://www.oracle.com/technetwork/java/index.html).

2. Make sure that you:

   • Have administrative permissions to install the J2SE Runtime Environment.

   • (For users installing the JRE on non-Western 32-bit machines) - Select a Custom Setup Type. In Custom Setup under feature 2 (Support for Additional Languages), select This feature is installed on local hard drive.

3. Close all instances of the web browser.

4. Log into OMi and access Service Health Top View. Verify that the Chinese or Japanese characters now appear correctly.

• Oracle and PostgreSQL databases only: If you use a CJK language in your browser, you must ensure that the Gateway Server machine running OMi has East Asian languages installed. On the machine on which the OMi Gateway Server is installed, select Control Panel > Regional & Language Options > Languages > Install files for East Asian languages.

• If you installed OMi on a non-English Windows operating system, the command line tool output may not be displayed correctly because the Windows and OEM code pages differ. This may not be the case on many Asian language systems, but is often experienced on non-English European systems.

  To fix this, configure the Windows Command Prompt so that a TrueType font is used and the OEM code page is the same as the Windows code page.

  In a Windows Command Prompt window (run cmd.exe):

  1. Right-click the title bar, select Properties, and open the Font tab.
  2. Change the font from Raster Fonts to a TrueType font, and change the font size if necessary (for example: select Lucida Console, 12 pt).
  3. If prompted, modify the shortcut to make the font change global.

  Note If you use other command line tools, such as PowerShell or Cygwin Bash, change the font for each of these tools separately.

  To change the codeset for the system, open the registry editor (regedit), and go to: Computer\HKEY_LOCAL_MACHINE\SYSTEM\
CurrentControlSet\Control\Nls\CodePage. If the values of ACP and OEMCP differ, edit OEMCP to the same value as for ACP, and reboot the system.

  Note If changing the OEM code page for the system is not acceptable, for each newly opened Command Prompt window, change the code page value using the command: chcp <APC value>.

• The installation path for all OMi components must not contain non-Latin characters.

• When content packs are available in more than one language, the language of content packs automatically loaded during OMi installation depends on the current locale of the host operating system. If there are matching content packs for the current locale, these are installed. If the locale does not have localized content packs, English content packs are used. Later, a user can upload the content pack in another language manually.

  At every Gateway Server startup, the contents of the following directory is checked: <OMi_HOME>/conf/opr/content/<locale of server>

  Any package that has not already been loaded, and that does not have unresolved package dependencies (references to packages, which are neither already loaded nor in the same folder), is loaded during this startup.

  The following directory is checked next: <OMi_HOME>/conf/opr/content/en_US

  Any content packs that were not uploaded from the first location are uploaded. This can result in mixed-language content.

  The packages are loaded with the standard import mode; already existing artifacts are not changed. Only new artifacts are added.

  Note Progress can be followed in the admin backend log file. The operation is done in the background and may still be in progress when a user logs in. The system prevents multiple content packages from being loaded at the same time.

• If you changed your system locale on Windows after installation, your system account might still have the wrong locale. Ensure that OMi processes run in the desired locale. On the machine on which OMi is installed, select Control Panel > Region > Administrative > Copy Settings and reboot the system.

• To work in a non-Latin-character language OMi environment, you can use an Oracle database, a Microsoft SQL Server database, or a PostgreSQL database. For details about the database character set configuration as well as a list of supported and tested database servers, see the OMi Database Guide.

• The SiteScope Database Query Monitor can connect to an Oracle database but the Oracle user names and passwords must contain only Latin characters.

• Email alerts sent with ISO-2022-JP encoding are supported only by an SMTP server running on a Windows platform. Use of this encoding affects all OMi servers.

• When using the default authentication strategy, Lightweight SSO, to authenticate users logging into OMi, user names and passwords can be in non-Latin characters.

• To support non-Latin characters in OMi databases, the encoding for databases must be defined as described in the OMi Database Guide.

• To support non-Latin characters in log files, set the log4j encoding property on the log4j configuration files.

  To write a specific log in UTF-8 encoding, do the following:

  1. Search the specific log name in log4j configuration at conf/core/Tools/log4j.

  2. In the properties file where this log file is configured, add the following property:

     log4j.appender.<appender name>.Encoding=UTF-8

     For example, the jboss_server.log configuration follows:

     #######################################
     ### define appender: jboss.appender ###
     #######################################
     # jboss.appender is set to be a FileAppender which outputs to log/jboss_server.log
     log4j.appender.jboss.appender=org.apache.log4j.RollingFileAppender
     log4j.appender.jboss.appender.File=${merc.home}/${log.file.path}/jboss_server.log
     log4j.appender.jboss.appender.MaxFileSize=${def.file.max.size}
     log4j.appender.jboss.appender.Encoding=UTF-8
     log4j.appender.jboss.appender.MaxBackupIndex=${def.files.backup.count}
     log4j.appender.jboss.appender.layout=org.apache.log4j.PatternLayout
     log4j.appender.jboss.appender.layout.ConversionPattern=${msg.layout}
     

• OMi does not support Custom Report names that contain more than 50 multibyte characters.

• The Page Component Breakdown report does not support URLs that contain multibyte characters. When specifying a URL and a location from which to run the breakdown, you must enter Latin characters in the URL box.

• Excel reports must have Latin-character file names when uploading to OMi running on a Chinese Simplified operating system. To view Excel reports, select Applications > User Reports > Report Manager.

• Reports downloaded from OMi to Excel cannot be displayed properly on an operating system whose language differs from the data language.

  To download Excel files with multibyte data when OMi is installed on an English-language machine, set the user.encoding entry in the <OMi_HOME>\AppServer\resources\strings.properties file to the correct encoding.

When exporting a CI instance to a PDF file, Japanese characters are not displayed in the PDF file. (Data Flow Management > Discovery Control Panel > Basic Mode. Run discovery. When discovery has finished, select a CIT in the Statistics Results pane. Click the View Instances button. In the Discovered by dialog box, select Export Data to File > Export Displayed CIs to PDF.)

• The SNMP notification method does not support multilingual text, and can only send a notification in the character set of the Gateway Server machine. This is because OMi uses SNMP version 1.0, which does not support multilingual data.

• Error messages in the Failed Transactions report do not display correctly when OMi runs on an English operating system and the Business Process Monitor runs on a Japanese operating system. To access the Failed Transactions report, select Applications > End User Management > Business Processes > Error Summary. Locate the General Errors table, and click a link to open the Failed Transactions window.

• OMi can store multilingual data in an Oracle database or a PostgreSQL database. However, a regular executable cannot usually accept multilingual data on the command line.

  The following table describes the procedures that you must perform to add multilingual data to the command line when running an executable file upon alert:

  Platform	Procedure
  Windows	To prevent multilingual data from being lost, write the application with a wmain function instead of a main function. You can also use another main-type function that can take command line parameters of type wchar instead of type char. Note: When you use the SubAlerts command line option, the created XML file does not include an encoding attribute, and the encoding is different from the default UTF-8 encoding.
  Linux	Inform the writer of the application that the parameters passed to the application must be encoded in UTF-8.

• An executable file that was created for a previous version of OMi is compatible with a multilingual version.

• There is no language pack installation. All translated languages are integrated into the OMi Multilingual User Interface (MLU).

• Data remains in the language it is entered in, even if the language of the web browser changes. Changing the language of the web browser on your local machine does not change the language of any data that was entered by a user.

• You cannot deploy a package if the server locale is different from the client locale and the package name contains non-Latin characters. For details, see the RTSM - Administer section.

• You cannot create a package that contains resources (for example, views and TQLs) having non-Latin characters in their names, if the server locale is different from the client locale. For details, see the RTSM - Administer section.

• In the Modeling Studio, you cannot create a new view if the view's name contains more than 18 Japanese characters. For details on creating new views, see the RTSM - Modeling section.

• The OMi server status HTML page appears only in English. It is not translated into any other language.

• In Workspaces, all page names are in English, regardless of the UI language selected.

• In reloading the Event Browser (HTML), no events are listed and Japanese view names are not displayed correctly if your Microsoft MS SQL Server database is not installed on a Japanese operating system. Make sure to install the MS SQL database on a Japanese operating system to fix the issue.

• To simplify creating a tool that is similar to an existing tool, you can create duplicates of any existing tool. The duplicate tool's name and display name are copy of <tool>. The "copy of" portion of the duplicate tool's name is not translated.