Is there an order to install the Sitecore 9 XP1 Topology?

Avatar de Vinicius

A powershell script to “simplify your installation” is provided by the Sitecore 9 Installation Guide, however, you can use a different way where you have to execute every JSON file individually and following a particular order, which is my preferred for now until I better understand the whole process.

After analyzing the JSON files, and post a question on the Sitecore StackExchange, and getting myself with tons of errors during the installations, I decided to create a relation table where would be easier to determine the requirements of every JSON file, then establish a proper order.

Sitecore XP1 Reference Table Requirements Installation Blog Vinicius Deschamps

Assuming you already have SQL Server and SOLR in-place, and based in the reference table above, I’ve determined the following order to install XP1 topology without getting stop due missing prerequisites.

  1. At the SOLR server, modify and run XConnect-Solr.json and Sitecore-Solr.json
  2. Create XConnect certificate – I’d recommend to download the XP0 topology and use XConnect-CreateCert.json for that, check the reason here in Sitecore StackExchange
  3. XConnect-xp1-collection.json
  4. XConnect-xp1-collectionsearch.json
  5. XConnect-xp1-referencedata.json
  6. XConnect-xp1-marketingautomation.json
  7. XConnect-xp1-marketingautomationreporting.json
  8. sitecore-xp1-rep.json
  9. sitecore-xp1-prc.json
  10. sitecore-xp1-cm.json
  11. sitecore-xp1-cd.json

I hope this helps you as it helps me!

Also, I’d recommend the following articles to get you asap working with Sitecore 9

And last but not least, I special thanks my friend João Neto, who just become Sitecore MVP 2018, and the one that provided initial directions in Sitecore StackExchange.

Thanks for reading!

And I’ll see you on my next post.

Photo by Mitchell Luo on Unsplash

Tagged in :

Avatar de Vinicius

15 respostas para “Is there an order to install the Sitecore 9 XP1 Topology?”

Deixe um comentário

O seu endereço de e-mail não será publicado. Campos obrigatórios são marcados com *