The instance must be running your site application (your customer-facing web application).
The instance repositories must be configured so ATG Knowledge users view the same data as customers accessing the site. To do this, the ATG Knowledge installation must use the same
JTDataSource
as the external site.Load Balancing must be configured for the actual number of clusters.
The instance must be configured to use locked caching in the
TicketingRepository
andProfileAdapterRepository
to guarantee that the live data viewed by ATG Knowledge users is always current. Refer to ATG Service Installation and Configuration Guide for information on configuring lock managers. Refer to the SQL Repository Caching section of the ATG Repository Guide for additional information on cache modes.Any commerce-related items (catalogs and price lists) must be read-only. Keep them synchronized across ATG instances by periodically publishing the current data to all instances simultaneously. For the order repository, however, the data is constantly being modified by customers, so all ATG instances must point to the same set of database tables.
If you are running ATG Knowledge Data Warehouse, ensure that the module is running in a separate JVM.