Gravatar for allison.bates@fisglobal.com

Question by abates100, Sep 21, 2015 1:55 PM

Remote Install of Coveo for Sitecore question

Can anyone clarify when or why to use the different install and configuration processes described in these 2 articles?

https://developers.coveo.com/display/public/SC201509/Installing+Coveo+for+Sitecore#InstallingCoveoforSitecore-Installationprocedure

https://developers.coveo.com/display/public/SC201509/Setting+Up+Coveo+for+Sitecore+in+a+Remote+Server+Configuration

We have one CD server that will also be the CES server and 2 CM servers that will utilize the search api.

Gravatar for allison.bates@fisglobal.com

Comment by abates100, Sep 21, 2015 1:57 PM

Got that backwards - CM server will host CES and serve 2 CD servers.

1 Reply
Gravatar for jflheureux@coveo.com

Answer by Jean-François L'Heureux, Sep 21, 2015 6:07 PM

Hi Allison,

The "Setting Up Coveo for Sitecore in a Remote Server Configuration" article is for when you install CES and the Sitecore CM on separate servers. This is not your case as CES will be installed on the same server as the Sitecore CM instance.

When installing on multiple Sitecore instances in a "farm", you should follow the "Installing Coveo for Sitecore in a CM/CD Configuration" documentation. Specifically, in your use case you would:

  • Install CES and the Coveo Search API on your Sitecore CM server at step 2.
  • Install the Coveo for Sitecore package on your Sitecore CM instance at step 3.
  • Manually deploy Coveo for Sitecore files on your 2 Sitecore CD instances at step 3 in the "Deploying Coveo for Sitecore on other Content Management and Content Delivery hosts" subsection.
  • Follow the procedure in the "Additional configuration steps for deploying Coveo for Sitecore on other Content Delivery hosts only" subsection on your 2 Sitecore CD instances.
Gravatar for allison.bates@fisglobal.com

Comment by abates100, Sep 22, 2015 9:43 AM

Thank you! We actually installed the package on each of the CD servers then edited the config files. The edits are a bit different in the CM/CD configuration so just a couple more questions.

Gravatar for allison.bates@fisglobal.com

Comment by abates100, Sep 22, 2015 9:50 AM

  1. Should the amqp://localhost:5682/ on the CD servers really be localhost not the CES server?
  2. Should the tag be populated on the CM/CES server? or just use what is displayed in the CES Admin tool? We have no 'pub' database just the defaults.
  3. Should the tag be populated on the CD servers or not?
Gravatar for jflheureux@coveo.com

Comment by Jean-François L'Heureux, Sep 22, 2015 11:09 AM

  1. With the <SkipSitecoreCredentialsUpdate>, <SkipSitecoreLoginCheck> and the <SkipFirstTimeSetupCheck> set to true on your CD instances, you don't need to set the <QueueUri>. This setting is only needed for the Sitecore CM to know where to send the RabbitMQ messages.
  2. The <SecurityProviderName> element won't be set automatically, you need to set it on all the Sitecore instances to the name of the automatically generated security provider for the CM in the CES Admin Tool
  3. You should set the <ServerUrl> on all the Sitecore instances as it is used to build search results URIs.
Ask a question