Portal Configuration Tool Guide

10.5 HotFix 2

Back Next

Supporting Additional Languages

You can support additional languages for the portal based on your business needs and the geographical region. For example, to support portal users in Eastern Europe, you can add Russian, Polish, Czech, or other Eastern European languages to the language bundle. After you add the languages and deploy the portal, the portal users can view the portal in the language of their choice.

Localize the following

Customer 360

resources and custom resources to the language that you want:

Labels and error messages

Metadata

Lookup table

For more information about localizing

Customer 360

resources and custom resources, see the

Informatica MDM - Customer 360 Installation and Configuration Guide

Export the language bundle from the Portal Configuration tool.

For more information, see Exporting the Language Bundle.

The language bundle is downloaded as a ZIP file.

To add a language to the portal, save a copy of the

bundle.properties

and

errors.properties

files either with the corresponding language code and country code or with the language code only.

For example, to add support for the German language, save a copy of the

properties

files with the following names:

bundle_de.properties

error_de.properties

To add support for the German dialect spoken in Austria, save a copy of the

properties

files with the following names:

bundle_de_at.properties

error_de_at.properties

In a text editor, open the corresponding localized files and add the localized string values to the files.

Compress the updated localized files to a ZIP file.

Import the language bundle to the Portal Configuration tool.

For more information, see Importing the Language Bundle.

To generate JSON files for the corresponding localized bundle files, perform the following steps:

At the command prompt, navigate to the following directory:

<MDM installation directory>/app/portal

Extract the contents of the

generic-portal.ear

file.

Navigate to the directory that contains the extracted files.

Extract the contents of

mdm.ui-portal-ui-0.0.1.war

and

mdm.ui-portal-config-0.0.1.war

files.

Navigate to the

locales

folder in the directories that contain the extracted files.

Use the English language JSON file,

translation_en.json

, as a reference and generate the JSON files for the respective localized bundle files.

For example, if the

PRODUCT_NAME

key in the English language JSON file contains the value

MDM Portal Configuration Tool

, then ensure that the corresponding key in the German JSON file contains the localized version

MDM-Portal-Konfigurationstool

as the value.

Ensure that the generated JSON files have all the values localized in the language that you want. Also, use the following formats to name the JSON files:

translation_<lang_key>.json

translation_<lang_key>_<country_code>.json

Add the JSON files that you generate to the respective

locales

folders.

Generate the

generic-portal.ear

with the newly added JSON files.

To update the changes, deploy the portal again.

For more information, see Deploying a Sample Portal.

Localizing a Portal

Download Guide