• United States
IBM?
  • Site map
IBM?
  • Marketplace

  • Close
    Search
  • Sign in
    • Sign in
    • Register
  • IBM Navigation
IBM Developer Answers
  • Spaces
    • Blockchain
    • IBM Cloud platform
    • Internet of Things
    • Predictive Analytics
    • Watson
    • See all spaces
  • Tags
  • Users
  • Badges
  • FAQ
  • Help
Close

Name

Community

  • Learn
  • Develop
  • Connect

Discover IBM

  • ConnectMarketplace
  • Products
  • Services
  • Industries
  • Careers
  • Partners
  • Support
10.190.13.206

Refine your search by using the following advanced search options.

Criteria Usage
Questions with keyword1 or keyword2 keyword1 keyword2
Questions with a mandatory word, e.g. keyword2 keyword1 +keyword2
Questions excluding a word, e.g. keyword2 keyword1 -keyword2
Questions with keyword(s) and a specific tag keyword1 [tag1]
Questions with keyword(s) and either of two or more specific tags keyword1 [tag1] [tag2]
To search for all posts by a user or all posts with a specific tag, start typing and choose from the suggestion list. Do not use a plus or minus sign with a tag, e.g., +[tag1].
  • Ask a question

How to develop rules with multiple languages and localizations?

270006BT54 gravatar image
Question by Miriam.Kaestner  (8715) | Oct 24, 2016 at 03:07 AM ibmodmodmdecisioncenterdecisionserverlanguage-translationlocale

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?

LiezlChin

People who like this

  1
Comment
10 |3000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster

1 reply

  • Sort: 
270006BT54 gravatar image
Accepted answer

Answer by Miriam.Kaestner (8715) | Oct 24, 2016 at 03:21 AM

Let me explain the concepts of NLS and localization in ODM:

  1. 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 *.brl file.

  2. The locale of any rule/ruleflow to be published to DC must match DC persistence locale.

  3. The persistence locale determines the language in which rules are stored in the Decision Center database.

  4. 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.

    http://localhost:9080/teamserver?dataSource=jdbc/rtsJP

  5. A BOM can be verbalized in more than one language (multiple *.voc files)

  6. RD creates/selects/displays the vocabulary according to workspace locale.

  7. 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.

  8. 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.

  9. Decision Server is locale independent. So you can deploy and run rules in any language on the same DS.

See also this answer.

Comment
LiezlChin
AmitShah

People who like this

  2   Show 2   Share
10 |3000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
270006HHSD gravatar image AmitShah (443)   Feb 07, 2017 at 08:57 AM 0
Share

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 ).

270006BT54 gravatar image Miriam.Kaestner (8715) AmitShah (443)   Feb 21, 2017 at 08:03 AM 0
Share

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.

Follow this question

94 people are following this question.

Answers

Answers & comments

Related questions

ODM 8.5.1 - Rules Publishing to Branches Issues 1 Answer

TADDM reports false positives for an ODM v8.5.1 installation 1 Answer

Is IBM ODM affected by the change of Japanese Era on May 1st 2019 ? 1 Answer

DC/DS profile creation failed - ODM 8.8.1.3 Linux 3 Answers

Project restricted for a user in DC but is visible in BC 2 Answers

  • Contact
  • Privacy
  • IBM Developer Terms of use
  • Accessibility
  • Report Abuse
  • Cookie Preferences

Powered by AnswerHub

Authentication check. Please ignore.
  • Anonymous
  • Sign in
  • Create
  • Ask a question
  • Spaces
  • API Connect
  • Analytic Hybrid Cloud Core
  • Application Performance Management
  • Appsecdev
  • BPM
  • Blockchain
  • Business Transaction Intelligence
  • CAPI
  • CAPI SNAP
  • CICS
  • Cloud Analytics
  • Cloud Automation
  • Cloud Object Storage
  • Cloud marketplace
  • Collaboration
  • Content Services (ECM)
  • Continuous Testing
  • Courses
  • Customer Experience Analytics
  • DB2 LUW
  • DataPower
  • Decision Optimization
  • DevOps Services
  • Developers IBM MX
  • Digital Commerce
  • Digital Experience
  • Finance
  • Global Entrepreneur Program
  • Hadoop
  • Hybrid Cloud Core
  • IBM Cloud platform
  • IBM Design
  • IBM Forms Experience Builder
  • IBM Maximo Developer
  • IBM StoredIQ
  • IBM StoredIQ-Cartridges
  • IIDR
  • ITOA
  • InformationServer
  • Integration Bus
  • Internet of Things
  • Kenexa
  • Linux on Power
  • LinuxONE
  • MDM
  • Mainframe
  • Messaging
  • Node.js
  • ODM
  • Open
  • PowerAI
  • PowerVC
  • Predictive Analytics
  • Product Insights
  • PureData for Analytics
  • Push
  • QRadar App Development
  • Run Book Automation
  • Search Insights
  • Security Core
  • Storage
  • Storage Core
  • Streamsdev
  • Supply Chain Business Network
  • Supply Chain Insights
  • Swift
  • UBX Capture
  • Universal Behavior Exchange
  • UrbanCode
  • WASdev
  • WSRR
  • Watson
  • Watson Campaign Automation
  • Watson Content Hub
  • Watson Marketing Insights
  • dW Answers Help
  • dW Premium
  • developerWorks Sandbox
  • developerWorks Team
  • Watson Health
  • More
  • Tags
  • Questions
  • Users
  • Badges