Oracle Waveset 8.1.1 Deployment Guide

Architectural Overview

Table 13–1 Components of Waveset Internationalization

File  

Description  

WPMessages.properties

Default message file located in $WSHOME/idm/web/WEB-INF/classes/com/waveset/msgcat. Shipped as part of the idmcommon.jar file.

Displays message text in English and loads by default unless you’ve customized your Waveset installation to behave otherwise. 

Waveset.properties

Located in $WSHOME/config.

To enable support for multiple languages, you must set Internationalization.enabled to true. (Default is true.)

System Configuration Object

Specify a custom message catalog 

Additional message file for each supported language 

Additional supported languages each require their own message file. WPMessages_xx_XX.properties, where xx represents the language and XX represents the country. For example, WPMessages_en_US.properties contains messages in American English. Each international catalog has its own .jar.


Note –

The following catalog entries control how the product name is displayed:

PRODUCT_NAME=Waveset
LIGHTHOUSE_DISPLAY_NAME=[PRODUCT_NAME]
LIGHTHOUSE_TYPE_DISPLAY_NAME=[PRODUCT_NAME]
LIGHTHOUSE_DEFAULT_POLICY=Default [PRODUCT_NAME] Account Policy

Typical Entry

Messages are contained in key/text pairs and contain three parts:

Each line in the resource array contains two strings. Translate the second quoted string on each line.

Certain strings to be translated contain special codes for data that is inserted into the string when it is displayed. For example, if you have the following string to translate:

UI_USER_CONNECT={0}, connected at 100 mbs

the rendered version could appear as jfaux, connected at 100 mb

Translations typically appear inside a browser, so it is appropriate to add HTML tags to format the string, as shown below:

_FM_ACCOUNT_ID_HELP=<b>Account ID</b><br>Enter a name for this user. This field is required.