How to add new locale to the Identity Applications on a Tomcat Server (Part 2)

How to add new locale to the Identity Applications on a Tomcat Server (Part 2)

This guide is intended for users who want to translate the Identity Manager HPD and UA into a language that is not part of the standard language support set.

In the first part I talked about how to add new locale to User Application driver and in the User Application WAR file.

This part is for localizing Home and Provisioning Dashboard (HPD) including the One SSO Provider (OSP) login page. Basicly the URL's /landing/* and /dash/*

Let's start from the first thing users are seeing, the OSP Login Page.

 

OSP Login Page


 

The strings can be found from
/opt/netiq/idm/apps/osp_sspr/osp/l10n-resources/osp-strings.jar

Unpack osp-strings.jar and get file WEB-INF/classes/oidp_custom_resources_en_US.properties for translation.

Translate the strings to Finnish and remember to rename the translated files to *_fi.properties. Place the new strings file to /tmp/osp/WEB-INF/classes/oidp_custom_resources_fi.properties

Add new strings to osp-conf.jar - file.

Create tmp directories for update
mkdir /tmp/osp/WEB-INF/classes -p
cd /tmp/osp

Copy .jar to update folder and update it with new strings file.
cp /opt/netiq/idm/apps/osp_sspr/osp/osp-conf.jar .
jar -ufv osp-conf.jar WEB-INF/classes/oidp_custom_resources_fi.properties

Stop idmapps, empty tomcat /temp and /work -directories
/etc/init.d/idmapps_tomcat_init stop
cd /opt/netiq/idm/apps/tomcat/temp
opt/netiq/idm/apps/tomcat/temp # rm -r *
cd /opt/netiq/idm/apps/tomcat/work
opt/netiq/idm/apps/tomcat/work # rm -r *

Copy osp-conf.jar on top of the current one. Remember to take backup before this.
cd /tmp/osp
cp osp-conf.jar /opt/netiq/idm/apps/osp_sspr/osp/osp-conf.jar

OSP update is now done, start idmapps
/etc/init.d/idmapps_tomcat_init start

Note: 
Login Page will be shown using the locale settings of the browser.

 

Landing Pages


 

The string can be found from file
/opt/netiq/idm/apps/UserApplication/l10n-resources/landing/landing-strings.jar

Unpack landing-strings.jar

Translate the strings to Finnish and remember to rename the translated files to *_fi.properties. Place the new strings file GwtUIStringsRsrc_fi.properties back inside of the jar. Put your modified .jar to /tmp/landing/WEB-INF/lib/landing-strings.jar

Add new strings to landing.war - file.

Create tmp-folders, copy landing.war to tmp for update, and update it with new strings .jar - file.
mkdir /tmp/landing/WEB-INF/lib -p
cd /tmp/landing
cp /opt/netiq/idm/apps/tomcat/webapps/landing.war .
jar -ufv landing.war WEB-INF/lib/landing-strings.jar

Stop idmapps, empty tomcat /temp and /work -directories
/etc/init.d/idmapps_tomcat_init stop
cd /opt/netiq/idm/apps/tomcat/temp
opt/netiq/idm/apps/tomcat/temp # rm -r *
cd /opt/netiq/idm/apps/tomcat/work
opt/netiq/idm/apps/tomcat/work # rm -r *

Delete /webapps/landing - folder and files.
cd /opt/netiq/idm/apps/tomcat/webapps/landing
/opt/netiq/idm/apps/tomcat/webapps/landing # rm -r *
/opt/netiq/idm/apps/tomcat/webapps/landing # cd ..
/opt/netiq/idm/apps/tomcat/webapps # rmdir landing

Copy landing.war on top of the current one. Remember to take backup before this.
/tmp/dash # cp landing.war /opt/netiq/idm/apps/tomcat/webapps/landing.war

Landing update is now done, start idmapps
/etc/init.d/idmapps_tomcat_init start

 

Dash Pages


 

The string can be found from file
/opt/netiq/idm/apps/UserApplication/l10n-resources/dashboard/dash-strings.jar

Unpack dash-strings.jar. Translate the strings to Finnish and remember to rename the translated files to *_fi.properties. Place the new strings file GwtUIStringsRsrc_fi.properties back inside to the jar.

Add new strings to dash.war - file.

Stop idmapps, remove tomcat temp and work content, remove /opt/netiq/idm/apps/tomcat/webapps/dash - folder and its contents.

Copy /opt/netiq/idm/apps/tomcat/webapps/dash.war to tmp for update, and update it with new strings dash-strings.jar using the same methods as with Landing Pages earlier, deploy new dash.war.

Dash update is now done, start idmapps.

 

Localize the Home Items


 

Landing and dash strings do not contain all the string, we need to translate strings from one more location.

Login to HPD (http://yourserver:8180/landing) with uaadmin.

Choose Edit from the Landing page.

Choose Localize from the Edit Home Items page.

Now you can see new locale fi - available.

locales5

Download the string file fi.properties

Add the missing Finnish Values to the file.

Upload the modified fi.properties - file back to the page.

Choose Back to edit

Choose I'm done

Now you have completed the localization of

  • One SSO Provider (OSP) Login Page

  • Home and Provisioning Dashboard (HPD)

  • UserApplication (UA) "old-interface"


That's all for now, good luck with your deployments.

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Top Contributors
Version history
Revision #:
1 of 1
Last update:
‎2015-07-01 00:06
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.