For each ATG Server instance, you must have at least one unique Endeca application and corresponding MDEX. For example, if you are configuring a publishing server and a production server, you will need a minimum of two Endeca applications and two MDEX instances. If your product catalog has data in multiple languages, the exact number of Endeca applications you have per server depends on your approach to indexing these languages, as described below.
One Language Per MDEX
In this configuration, you have one MDEX for each language for each server. For example, if you have three languages—English, German, and Spanish—and you have two servers—Content Administration and Production—you must have six Endeca applications:
Content Administration/English
Content Administration/German
Content Administration/Spanish
Production/English
Production/German
Production/Spanish
You must include the language code in the name to identify each Endeca application. For example, the names for the Content Administration-related Endeca applications would be ATGCAen, ATGCAde, and ATGCAes, where en, de, and es represent the language code and ATGCA is the base name shared by all of the applications. Likewise, the names for the Production-related Endeca applications would be ATGProden, ATGProdde, and ATGProdes.
As you create the Endeca applications, using the deployment template, be sure to specify the correct language code for each application. Also, be sure to provide unique ports for the LiveDgraph, AuthoringDgraph, and LogServer for each application.
All Languages in a Single MDEX
If you plan to have all languages indexed in a single MDEX, you only need to create one Endeca application for each ATG server instance. For example, if you have Content Administration and Production server instances, you must create two Endeca applications, one for each server instance. As you create the Endeca applications using the deployment template, be sure to specify the default language code for each application and provide unique ports for the LiveDgraph, AuthoringDgraph, and LogServer.
In the single MDEX situation, use the language code of the default language for the record stores in the Endeca application name. For example, if you have Content Administration and Production servers on the ATG side and English is the default language for the records stores, create ATGCAen and ATGProden applications on the Endeca side. Then, specify the default language (in this case, en) in the /atg/endeca/index/DataDocumentSubmitter component’s defaultLanguageForRecordStores property for each ATG server instance:
defaultLanguageForRecordStores=en
