In a multisite environment, all Web sites supported by your ATG instance typically use the same pages (for example, all sites have the same login page, possibly called login.jsp). The pages contain code that controls the display of content, making it appropriate for each site. Be aware that any slot you add to a page will therefore display the same content on all your sites unless you configure it otherwise.
There are several methods for configuring slots to display site-specific content.
One efficient way is to use a single slot component on all sites and add content to it through a targeter that has site-specific rules. Create a scenario that uses the site-specific targeter to fill the slot. For a description of site-specific targeters, refer to the ATG Business Control Center User's Guide. For more information on creating scenarios, refer to the ATG Personalization Guide for Business Users.
You can create a different slot for each site and write page logic that checks the site context and determines which slot to render for the current site. This approach is less efficient than the single slot method if you have many sites to maintain.
Note: For slots that are filled by a multisite targeter, be aware of the following behavior with session-scoped slots. A session-scoped slot is filled with the items on the current site when the slot is first requested. Subsequent requests will use the items that were filled on the first request, regardless of the current site. The following situation is therefore possible: a user logs into Site A and views items from the current site via a session-scoped slot. When the user switches to Site B, the slot still displays items from Site A.
For more information on site context and working with pages in a multisite environment, refer to the ATG Multisite Administration Guide.
