In an ATG multisite installation, identify three strategies that ATG employs to determine request is
associated with.
A.
sticky session based
B.
sticky site parameter based
C.
domainbased
D.
path based
E.
configuration File
Explanation:
A multisite application must be able to quickly determine what site a given request is
associated with. To this end, the ATG platform supports two main URL management strategies:
* In a domain-based strategy(C)
* In a path-based strategy (D)
B: RequestParameterRuleFilter checks the request URL for two query parameters:
* pushSite is set to a site ID, which is returned by the rule filter’s filter() method.
* stickySite, if set to setSite, makes the pushSite-specified site sticky for the current session.
Unless explicitly reset or unset, the sticky site is used for all subsequent requests during that
session.
Note: RequestParameterRuleFilter
Based on the class atg.multisite.PushedSiteParamFilter, the
component /atg/multisite/RequestParameterRuleFilter is the first rule filter to execute. This filter
processes request query parameters that set the current site, and specify it as a sticky site that
persists throughout the session of that request.