How to Approach Internationalized Data Configuration in MDEX 6.3.0 and Later (Doc ID 1560484.1)

Last updated on AUGUST 04, 2015

Applies to:

Oracle Commerce Guided Search / Oracle Commerce Experience Manager - Version 6.2.2 and later
Information in this document applies to any platform.

Goal

Beginning in MDEX 6.3.0, the approach to managing internationalized data inside Endeca changed due to new implementation of Oracle Language Technology (OLT).  OLT replaced the older technology used to handle internationalization inside Endeca.  This means that previously acceptable approaches to managing data for some languages within Endeca need to be adjusted for the new versions.  Chinese, Japanese, and Korean are examples of long-supported languages within Endeca that require different implementation considerations in MDEX 6.3 OLT and later, where old approaches may not suffice.  This article refers to all languages that utilize the OLT functionality as opposed to the legacy "latin-1" functionality as described in the Advanced MDEX Development documentation.

For example, in previous Endeca versions it was acceptable to use "mixed" internationalized data within a single index by to tokenizing multiple kinds of language data on a per-property or a per-record basis using specific language identifiers.  Is this still an acceptable approach on MDEX 6.3 and later for languages that are handled via OLT?

 

 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms