If you use the same MDEX for all languages, you must create a single EAC application and a single set of record stores. In this case the language code is the code for the default language of the record stores. So if your catalog data is in English, German, and Spanish, and you want to index all languages in a single MDEX with English as the default language, your application name would be ATGen (assuming the endecaBaseApplicationName properties are set to ATG), and the record stores would be named ATGen_en_data, ATGen_en_dimvals, and ATGen_en_schema.

You specify the default language for the record stores by setting the defaultLanguageForRecordStores property of the /atg/endeca/index/DataDocumentSubmitter component to the two-letter code for the language. For example:

defaultLanguageForRecordStores=en

Several other components have a defaultLanguageForRecordStores property that links to this value. For example, the properties file for the /atg/endeca/index/commerce/EndecaScriptService component includes the following:

defaultLanguageForRecordStores^=\
/atg/endeca/index/DataDocumentSubmitter.defaultLanguageForRecordStores

The schema records generated in this case are the same records that would be generated in the multiple-MDEX case for the first locale listed in the /atg/endeca/index/commerce/SchemaExporter component’s locales property. The data records generated include the records for all of the listed locales, and each data record includes a product.language property that identifies the language of the record. The language name is given in its own language. For example, the value for the German language is Deutsch.

The dimension value records consist of the same set of records that would be generated for each language in the multiple-MDEX case, but the records generated by the /atg/endeca/index/commerce/RepositoryTypeDimensionExporter component contain additional properties for the translated display names of the repository item types. These properties are named dimval.prop.displayName_language-code, where language-code is the two-letter language code associated with one of the specified locales. For example:

<PROP NAME="dimval.prop.displayName_en">
  <PVAL>Category</PVAL>
</PROP>
<PROP NAME="dimval.prop.displayName_es">
  <PVAL>Categoría</PVAL>
</PROP>
<PROP NAME="dimval.prop.displayName_de">
  <PVAL>Kategorie</PVAL>
</PROP>

If the multiLanguageSynonyms property of the RepositoryTypeDimensionExporter component is set to true, then additional Endeca record properties are generated to indicate that all translations of the same repository type are synonyms for searching. For example:

<PROP NAME="dimval.search_synonym">
  <PVAL>Category</PVAL>
</PROP>
<PROP NAME="dimval.search_synonym">
  <PVAL>Categoría</PVAL>
</PROP>
<PROP NAME="dimval.search_synonym">
  <PVAL>Kategorie</PVAL>
</PROP>

Copyright © 1997, 2012 Oracle and/or its affiliates. All rights reserved.

Legal Notices