Internationalization in Endeca Server
With the release of Endeca Server 7.5.1, the MDEX engine takes a huge leap forward when it comes to supporting a wide variety of languages for Data Discovery applications. The new version supports 22 languages, up from 7 in the previous version. Supporting these new languages is a huge step forward, but the way in which langauages are implemented and supported inside of Endeca Server is what makes this such a big deal.
Going underneath the hood for the moment, a request to create an attribute in an Endeca instance typically gets issued from Integrator. To get really deep, the XML that gets sent to Endeca Server in OEID 3.0 might look something like this:
If you take a careful look above, you’ll notice that I was able to specify a property called Language (well, mdex-property_Language). What this allows you to do is specify a language at the individual attribute level, allowing a single MDEX to serve multiple sets of content from the same instance. This opens up all sorts of possibilities when it comes to supporting multiple languages in your application. The attribute I’ve created above will support the Thai language.
We’re currently limited from discussing some of the things that are coming to further enable internationalization until OEID 3.0 Studio is fully released, per our agreements with Oracle. But, you can just imagine the power of augmenting individual attributes and all of their capabilities (type ahead searchability to use one small example) with a language component that is specific to that attribute, rather than an entire index. As more and more components of the solution are released, we’ll have a ton more to say so stay tuned.
Note: We were asked to remove some posts you may have previously seen on our blog by Oracle as they referred to information that had not yet been made public. They will be returning to the blog over the coming weeks as OEID 3.0 is released.