To integrate with your Oracle Commerce Platform environment, you must have at least one EAC application and a corresponding MDEX. If your GSA repositories have data in multiple languages, the number of EAC applications you have depends on your approach to indexing these languages, as described below.

One Language per MDEX

In this configuration, you have one EAC application and a corresponding MDEX for each language. For example, if you have three languages—English, German, and Spanish—you must have three EAC applications.

In this case, you provide a base application name that is used for all three EAC applications. By default, the names of the applications for the different languages are distinguished by adding the two-letter code for the language to the base application name. So, for example, if the base name is ATG, the names of the EAC applications would be ATGen, ATGde, and ATGes. (Note that you can override this naming convention if you prefer; see Configuring the ApplicationConfiguration Component.)

As you create the EAC 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 EAC application. In this case, the default name of the application is the base application name plus the two-letter language code for the default language for the application; for example, ATGen. (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 Oracle Commerce Platform server instance:

defaultLanguageForApplications=en

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