The Core of the Site

It isn't uncommon when you open up the Experience Analytics dashboard hoping to see some beautiful graphs and charts showing analytics data and boom! It welcomes you with the ugly red lines: I am usually very calm when dealing with errors in this dashboard because I have seen many root causes and found the fixes for them. Usually they are caused by certificate issues here or there . But this time looking at the log in the website, it shows a brand new error: 30240 10:24:37 ERROR [Sitecore Services]: HTTP GET URL http://mydomain.dev.local/sitecore/api/ao/aggregates/all/0751EFD8564F40A38083EF5C6E194247/-3191897772735422194?&dateGrouping=by-auto&&dateFrom=18-01-2020&dateTo=16-04-2020&keyGrouping=by-key Exception System.ArgumentNullException: typeKey should not be null. Parameter name: typeKey at Sitecore.Framework.Conditions.RequiresValidator`1.ThrowExceptionCore(String condition, String additionalMessage, ConstraintViolationType type) at Sitecor

Warning:  The post here contains the author's own opinions and suggestions. They may not conform with best practices from Sitecore. Apply them at your own risks. If you have not read part 1, check out the link here first . Otherwise, delve down to the steps below. 1. Install DB server with MS SQL & SOLR The installation of MS SQL 2016 and SOLR 7.5.0 need no introduction. You can easily find the guide here: https://docs.microsoft.com/en-us/sql/database-engine/install-windows/install-sql-server?view=sql-server-ver15 or there: https://lucene.apache.org/solr/guide/7_5/installing-solr.html To install SOLR as a service, check out step 5 in here: https://blogs.perficient.com/2017/10/26/setup-and-basic-preparation-for-sitecore-9-installation/ Assuming that you will use the default port 8983 for installing SOLR in this step (and subsequent steps) Make sure that when installing MS SQL server, you are installing in mixed authentication mode so you will have SQL admin

Warning: The post here contains the author's own opinions and suggestions. They may not conform with best practices from Sitecore. Apply them at your own risks. As a developer, you all are familiar with installing Sitecore XP as a standalone system. Meaning installing everything on a single server that handle everything: Content Delivery, Content Management, Database, SOLR Engine, etc. However it might not work so well on a production environment when you have thousands of visits per day unless your system is deployed on a blade server with 20 cores processor. In most scenarios, you will have a few servers to play with. In a recent project that I work on, I was given 3 servers to setup the system. Obviously this is the initial topology that I came up with: But in Sitecore XP 9.2, you don't just have CD, CM roles. There are tons of other roles that came with this version such as xConnect Collection, xDB Processing, Marketing Automation Engine and many more. How could