You must do some manual editing to configure communication between any server instances you create and the EAC applications that support them. In the CommerceAccelerator/Applications/application-name/src/main/config directory, make the following edits:

  1. In the /atg/endeca/ApplicationConfiguration.properties file, uncomment and edit the baseApplicationName , locales, and applicationKeyToMdexHostAndPort properties to reflect your application’s requirements, for example:

    baseApplicationName=NewStore
    locales=en_US
    applicationKeyToMdexHostAndPort=default=localhost:15000

    For a multiple EAC application environment, the applicationKeyToMdexHostAndPort property would look similar to the following:

    applicationKeyToMdexHostAndPort=en=localhost:15000,de=localhost:16000,es=localhost:17000

    And the locales property would look similar to this:

    locales=\
      en_US,\
      de_DE,\
      es_US

  2. In the /atg/endeca/assembler/AssemblerApplicationConfiguration.properties file, edit the assemblerContentBaseDirectory property to reference the location where your Assembler application export archive files are kept. For example:

    assemblerContentBaseDirectory=C:/Endeca/Apps/application_export_archive

    IMPORTANT: Use forward slashes for this path, even on Windows.

  3. If your environment has multiple EAC applications, then the default configuration of the /atg/endeca/assembler/admin/EndecaAdministrationService component must be changed as follows:

    Note: Using the MultiAppAdministrationService component means that storeFactories are automatically generated at run-time and do not need to be manually configured unless your application requires you to explicitly create them.

  4. In the /atg/multisite/DefaultSiteRuleFilter.properties file, uncomment and configure the defaultSiteId property to specify the site ID for your default site as defined in Site Administration.

Note: For more information on the ApplicationConfiguration , AssemblerApplicationConfiguration, and EndecaAdministrationService components, see the Platform-Guided Search Integration Guide.


Copyright © 1997, 2016 Oracle and/or its affiliates. All rights reserved. Legal Notices