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. Each application name should consist of a base name that is common to all of the applications, plus a two-letter language code that is unique to each one. The base name is used to associate the applications, and must match the value of the endecaBaseApplicationName property of the EndecaScriptService component and the document submitter components. (This is handled automatically when you configure your ATG environment using CIM.) The language code is used to distinguish the individual applications by language.

So, for example, if the endecaBaseApplicationName properties are set to ATG (the default), and catalog data is in English, German, and Spanish, the three applications would be named ATGen, ATGde, and ATGes.

The record stores for an EAC application use the following naming convention:

application-name_language-code_record-store-type

So for the ATGes application, the record stores are named ATGes_es_data, ATGes_es_dimvals, and ATGes_es_schema.


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

Legal Notices