If you use a separate MDEX for each language, you must create a separate EAC application and a corresponding set of record stores for each MDEX. By default, the name of each application is the value of the baseApplicationName property of the /atg/endeca/ApplicationConfiguration component plus the two-letter code for the application’s language.
So, for example, if the baseApplicationName property is set to ATG (the default), and catalog data is in English, German, and Spanish, the three applications would be named ATGen, ATGde, and ATGes.
If you do not want to use the default application naming convention, use the keyToApplicationName property of the /atg/endeca/ApplicationConfiguration component to map the application keys to the names of the applications. For example:
keyToApplicationName=\
en=MyEnglishApp,
es=MySpanishApp,
de=MyGermanApp
The record stores for an EAC application use the following naming convention:
application-name_language-code_record-store-type
So for the MySpanishApp application, the record stores are named MySpanishApp_es_data, MySpanishApp_es_dimvals, and MySpanishApp_es_schema.
For more information about application keys and application naming, see Creating the Endeca Applications.
