The instance must be running your customer-facing Web application

The instance repositories must be configured so Knowledge Manager users view the same data as customers accessing your sites. To do this, the Knowledge Manager installation must use the same JTDataSource as external sites

Load Balancing must be configured for the actual number of clusters

The instance must be configured to use locked caching in the TicketingRepository and ProfileAdapterRepository to guarantee that the live data viewed by Knowledge Manager users is always current. Refer to 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 Knowledge Manager Data Warehouse, ensure that the module is running in a separate JVM