Designer provides an easy way to localize the display labels defined in provisioning objects. You can provide localized string values whenever you see the button in Figure 2-3.
Figure 2-3 Localize Strings Button
When you click this button, Designer displays the Localization dialog box shown in Figure 2-4.
Figure 2-4 Localization Dialog Box
Table 2-3 Localizable Objects
You must provide a display label for the User Application driver’s default language, or you will encounter the following runtime error: The resource resolver com.novell.soa.common.i18n.LocalizedMapResolver did not return a resource for the default locale of <locale>. It is required that a resource exist for the default local.
The locale configuration is stored in the driver’s <default-locale> element in the AppConfig.AppDefs.locale-configuration XMLData attribute.
You can localize the display labels in any language displayed in the localization dialog box. The supported languages are defined in the User Application driver. You can modify the list of supported locales as described in Section 2.9, Specifying Locales and Localization Resource Groups.
The directory abstraction layer editor provides multiple ways to localize abstraction layer definitions. You can access the localization dialog boxes in these ways:
Table 2-4 Ways to Access the Localization Dialog Boxes
Designer provides a wizard that lets you export all of the display labels in your User Application project to an XML or properties file that you can localize and import back. You can export an entire driver, all directory abstraction layer or provisioning request definitions, or a single object at a time.
To export display labels:
To launch the Export Localization Data Wizard, right-click a container node or an object in the Provisioning view.
Select
.Fill in the fields as follows:
Click
. Designer displays a message describing the result of the export operation.To import localized files:
To launch the Import Localization Data Wizard, right-click a container node or an object in the Provisioning view.
Select
.Fill in the fields as follows:
Click
to complete the import. Designer displays a status dialog box that describes the results including any errors reading the files and any warnings about display label keys that are unused because no match was found.