Set up the Sitecore Infrastructure
This article provides guidelines on how to set up a Sitecore scaled environment. From a server infrastructure perspective, you don’t need to give any particular consideration to Coveo for Sitecore.
A content management instance is a type of Sitecore instance used for authoring Sitecore content. The content management hosts aren’t publicly accessible from the web.
A content delivery instance is a type of Sitecore instance used solely to show the website publicly. Sitecore content authoring tools should be disabled on these instances.
This service is responsible for indexing and querying documents. The Coveo Platform scales by nature (see High Availability in Coveo for Sitecore).
Sitecore Infrastructure Setup
The following diagram, borrowed from the Sitecore Scaling Guide, shows how to implement an environment composed of two content management hosts, two content delivery hosts, and an additional database (
pub) that’s used for the public website. All databases are installed on a single SQL Server host.
The environment is composed of the following hosts:
- SQL: this host holds all the databases. Web could have an SQL cluster with several hosts; it would be the same in Sitecore.
- CM1 & CM2: the content management hosts.
- CD1 & CD2: the content delivery hosts.
See the Sitecore Scaling Guide to replicate and configure the Sitecore infrastructure described above.
The above setup isn’t mandatory, and yours will most likely differ, but it will be used as an example for the rest of the scaling guide.
Once your Sitecore ecosystem is all set up, you may proceed to deploying Coveo for Sitecore on your main content management instance (see Prepare the Main Sitecore Content Manager for a Scaled Environment).
You should also read the Leading Practices When Deploying Coveo for Sitecore.