Different routing options are supported by different classes that implement the atg.endeca.configuration.ApplicationRoutingStrategy interface. There are three main classes in the atg.endeca.configuration package that implement this interface:
SingleApplicationRoutingStrategySiteApplicationRoutingStrategyGroupingApplicationRoutingStrategy
The various routing options and the ApplicationRoutingStrategy classes that support them are summarized in the following table:
Option | Description | Routing Strategy |
|---|---|---|
One EAC application | All records are directed to a single EAC application, regardless of the language or site. |
|
One language per EAC application | Each language’s records are directed to a separate EAC application. If there are multiple sites, all records for an individual language are directed to the language’s EAC application, regardless of the site. |
|
One site per EAC application | Each site’s records are directed to a separate EAC application. If there are multiple languages, all records for an individual site are directed to the site’s EAC application, regardless of the language. |
|
One combination of site and language per EAC application | Records for each combination of site and language are directed to a separate EAC application. For example, if there are five sites and three languages, there may be as many as 15 EAC applications. (There may be fewer if not all of the sites include all three languages.) |
|
Arbitrary grouping of sites per EAC application | For example, there are five sites, with records for two sites directed to one EAC application, and records for the other three sites directed to a second EAC application. If a site has multiple languages, all records for the site are directed to the site’s EAC application, regardless of the language. |
|
