For each ATG Server instance, you must have at least one unique Endeca application and corresponding MDEX. For example, if you are configuring a ATG Content Administration server and a production server, you will need a minimum of two Endeca applications and two MDEX engines. If your product catalog has data in multiple languages, the 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:

Each ATG server should use a different Endeca base application name, which by default is used for all of the applications associated with that server. For example, you could set the base application name for the Content Administration server to ATGCA, and set the base application name for the Production server to ATGProd. By default, the names of the applications for the different languages on a given server are distinguished by adding the two-letter code for the language to the base application name. So, for example, the names of the Content Administration-related Endeca applications would be ATGCAen, ATGCAde, and ATGCAes, and the names of the Production-related Endeca applications would be ATGProden, ATGProdde, and ATGProdes. (Note that you can override this naming convention if you prefer; see Configuring the ApplicationConfiguration Component.)

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. Each ATG server should use a different Endeca base application name; for example, you could set the base application name for the Content Administration server to ATGCA, and set the base application name for the Production server to ATGProd. By default, the name of the application is the base application name plus the two-letter language code for the default language for the application; for example, ATGCAen and ATGProden. (Note that you can override this naming convention; see Configuring the ApplicationConfiguration Component.) Be sure to specify the default language (in this case, en) in the /atg/endeca/ApplicationConfiguration component’s defaultLanguageForApplications property for each ATG server instance:

defaultLanguageForApplications=en

As you create the Endeca applications using the deployment template, be sure to provide unique ports for the LiveDgraph, AuthoringDgraph, and LogServer.