Note: For a general overview of multisite architecture, and detailed information about setting up a multisite environment, see the ATG Multisite Administration Guide.

When an Oracle ATG Web Commerce web server receives a request in a multisite environment, the request handling pipeline servlet SiteContextPipelineServlet (atg.multisite.SiteContextPipelineServlet) evaluates the request to determine the identity of the Oracle ATG Web Commerce site associated with it. That identity enables delivery of site-specific information in the server response. It is also important to maintain a site’s identity in order to differentiate it from other Oracle ATG Web Commerce sites that the user might visit during the same session.

Broadly speaking, SiteContextPipelineServlet performs the following tasks:

  1. Derives a site ID from the request URL.

  2. Determines whether site information is available for requests.

  3. Passes the site ID to the SiteContextManager and SiteSessionManager components:

    • The SiteContextManager (atg.multisite.SiteContextManager) creates a request-scoped SiteContext component, which gives the request thread access to site properties.

    • The SiteSessionManager (atg.multisite.SiteSessionManager) associates the site with a session-scoped SiteSession component, which maintains information about the site during the current session.

The following graphic illustrates this process and highlights components that play important roles. Later sections in this chapter describe these components in greater detail.