How to develop rules with multiple languages and localizations?
Client is having the ODM environment (Decision Center and Decision Server) in Japanese locale for their existing application landscape. Now, for the new program, they would like to use the same Decision Center having Japanese locale.
Issue we observed is that if we develop code in English locale within Rule Designer, we could NOT PUBLISH the code to Client Decision Center due to locale mismatch.
Does the above observation mean that client would have to procure English Locale DC for any code developed in English (irrespective of the locale changes done post Development in Rule Designer)?
Does IBM recommend any alternate solution in order to have development being still done in English but manage/govern/develop concurrently in Japanese as Client Team would like to reuse their existing Decision Center (JPN Locale) as long term strategy?
Are there any MIGRATION TOOLS available to convert English developed rules before publishing to DC which is JPN Locale?
As you know DC has locale constraint "that both RD & DC should be in same LOCALE", is there any similar constraint for DS (decision server) too?
Let me explain the concepts of NLS and localization in ODM:
Each rule or ruleflow has a locale which is set to workspace locale when artifact is created in Rule Designer. It can be manually edited in
*.brlfile.The locale of any rule/ruleflow to be published to DC must match DC persistence locale.
The persistence locale determines the language in which rules are stored in the Decision Center database.
You can have more than 1 DC database for the same DC application. Each DC database can have a different persistence locale. In the URL, you specify which datasource should be used, e.g.
A BOM can be verbalized in more than one language (multiple
*.vocfiles)RD creates/selects/displays the vocabulary according to workspace locale.
In DC Enterprise Console or Business Console, the user can individually set language in "Options". Menu entries are then shown in this language. Rule content is shown in persistence locale of DC database.
- Translation of either a vocabulary or existing rules is a manual
process:
change your RD locale to jp_JP
open your workspace that contains your project.
connect to DC
synchronize the BOM to get jp_JP vocabulary.
close RD
using a text editor (notepad++ for instance) replace known sentences (if then else set print definition less than ...)
open RD and manually correct remaining rules in error.
Decision Server is locale independent. So you can deploy and run rules in any language on the same DS.
See also this answer.
Hi Miriam,
Thanks for the detailed explanation. Can you also tell me if its possible to edit the rule content/values .
For example if the rule says :
the customer status is " Highly Valued Customer "
The content " Highly valued customer " must appear in different locale ( Say French ) and when edited in future , must use that particular locale(French ).
Hi @AmitShah if in your example, customer status is a dynamic domain with values stored in Excel, you can define label and documentation columns for different locales.