ShowTable of Contents
Overview of Multilingual Solution
Configuring Multilingual Solution (MLS) in IBM WebSphere Portal Web Content Manager (WCM) will enable a site to translate content to different locales and regions. This
will help site users to display content in their preferred language. MLS in Web Content Manager provides a set of tools to translate and manage the localized and
Now we will see the steps to configure MLS in WCM. The steps which are explained in this article are done on a stand-alone linux server. If it is a clustered setup, then
the steps needs to be repeated for every node in the cluster. Here, we are configuring WCM to enable it as localized site.
1. Edit wkplc.properties file, found in Portal under /opt/IBM/WebSphere/wp_profile/ConfigEngine/properties directoy.
2. Set the WasPassword and PortalAdminPwd password in wkplc.properties file.
3. Go to wp_profile_root/ConfigEngine directory. Run the below ConfigEngine task. This is shown in Figure 1.
Figure 1. Run the ConfigEngine task register-wcm-mls
4. Run the ConfigEngine task deploy-wcm-mls. This is shown in Figure 2.
Figure 2. Run the ConfigEngine task deploy-wcm-mls
5. If the server contains virtual portals, then run the following task for each virtual portal on your server:
./ConfigEngine.sh import-wcm-mls-data -DVirtualPortalHostName=VirtualPortalHostName -DVirtualPortalContext=VirtualPortalContext
6. Restart Portal Server.
7. In WCM, the content is stored in different libraries. The default language of the library is English. If you want to translate the content in a library to different locales,
then you must create library for different locales. While creating a library, choose the language appropriately. For example, I have a library test_EN with language selected
as English during library creation. If I want the site to be available in Spanish language, then create a library test_ES with language selected as Spanish.
8. Login to Portal. Go to Administration - Portal Content. Copy the content of base locale library (test_EN) to other languages using the 'Multi Locale Solution Library Copy' portlet.
This is shown in Figure 3. Here, Locale is the language of the new library which you want to copy content from Source Library.
Figure 3. Multi Locale Solution Library Copy portlet
9. After you copy the content to other locale libraries, any content that is created or modified in any library is not in synchronous with other locale libraries. To make the content synchronous between locale libraries, you need to either copy or link content. Now, we will see how to copy or link a content from Base library (English locale) to other locales. Go to WCM Authoring Portlet and update the Configuration settings to add the MLConfiguration_v7 library to the list of selected libraries.
10. Create a new Content using the Authoring Template(AT) MLConfiguration_v7 / LocalizedConfigurationFileAT. This is shown in Figure 4.
Figure 4. Create New Content using Authoring Template LocalizedConfigurationFileAT
11. Set the content location as Libraries > MLConfiguration_v7 > Content > ConfigurationHome > ConfigurationData. Content Name as 'MLSConfiguration'. In the 'Base
Content Library' field, enter the English language library 'test_EN' and in the field 'Content Libraries', enter all the locale libraries 'test_En, test_ES', Set the 'Has
Regionalizations' field as false. Enter the owner name in 'Content Library Owners' field. Here, wpsadmin is the Portal Administrator. Save and Close Content. This is
shown in Figure 5.
Figure 5. Create New Content 'MLSConfiguration'
12. For each library referenced in each multilingual configuration file, create a link component directly under the Components folder that references the multilingual configuration file:
For references to a localized multilingual configuration file, the link component name must be MLConfFileReference.
For references to a regionalized multilingual configuration file, the link component name must be RegionalizedMLConfFileReference.
The ALL_USERS group must be assigned to the User role in the component access controls.
This is shown in Figure 6.
Figure 6. Create link component referencing MLConfiguration link content in library test_EN, test_ES
13. In the base locale library 'test_EN', create an Authoring Template 'MyMLSAT'. Under 'Manage Elements', create a 'Rich Text' Element named 'Body' and 'Text'
Element named 'ML Translations'. This is shown in Figure 7.
Figure 7. 'Manage Elements' section in Create New Authoring Template 'MyMLSAT'
14. In the same AT 'MyMLSAT', go to 'Default Content' tab. In the 'ML Translations' Text Element, click on the properties icon, and choose 'Text Provider' as
'ML Text Provider'. Set the 'Custom JSP' field to the following value (for the Auto load version):
This is shown in Figure 8.
Figure 8. 'ML Translations' section in Create New Authoring Template 'MyMLSAT'
15. In the 'test_EN' library, create New Workflow 'MLWorkflow' with stages - Draft Stage, Publish Stage, Expire Stage, MLConfiguration_v7 / Delete (ML Delete
Workflow stage). This is shown in Figure 9.
Figure 9. Create New Workflow 'MLWorkflow'
16. In the same AT 'MyMLSAT', go to 'Default Content Properties' tab and associate 'MLWorkflow' with this AT.
17. The next step is to create a content and copy or link it to other locales, so that the created content gets translated to other locales as well. Create a new Content
'MyContent' using 'MyMLSAT'. Here, you will notice that there is a section 'ML Translations' which displays the multiple locale libraries for this base locale library
'test_EN'. From the 'ML Translations' section, in the row for Base locale, either you can copy or link the content to other languages. This is shown in Figure 10.
Figure 10. Create New Content in 'test_EN' library using 'MyMLSAT'
19. The content gets moved in the Workflow stages from Draft -> Publish -> Expire and then ML Delete Workflow Stage. If you have linked the content to other locale libraries, then you will notice that in ML Delete Workflow stage, the content in 'test_EN' library and its corresponding reference in 'test_ES' library gets deleted.
This article described the minimal steps required to configure a Multilingual Solution in IBM Web Content Manager 8.5. Now, you will have a clear understanding of MLS,
its configuration and the steps to translate a content to other languages.
About the author
Malarvizhi (Malar) Kandasamy is a Senior Staff Software Engineer who has worked at IBM since April 2005 and on WebSphere Portal since 2006,
with more than 13 years of experience in the software industry. She is an IBM Certified Solution Designer for Content Manager v8.3, an IBM Certified
Database Associate for DB2 v9, a Sun Certified Java Programmer 1.5, and an IBM Certified Lotus WebSphere Portal Administrator v6.1. She has
written several articles on WebSphere Portal and earned a distinction in Bachelor degree in Computer Science and Engineering from Madras
University in 2000. You can reach her at email@example.com.
1. Refer WebSphere Portal documentation: IBM Web Content Manager Multilingual Solution
2. Check this Article on Multilingual Solution: Realistic Example and Hands-on Step-by-Step Guide for WCM Multi-locale Delivery
3. Refer documentation on Configuring a multilingual system: Configuring a multilingual system