If you are using Sitecore 9 with Solr, you are most likely (should) be using Solr over SSL/HTTPS. Self-Signed Certificates are an option in non-Production environments but in the following scenarios you should use a Public Certificate Authority: Production on IaaS Azure AppServices with Solr on IaaS (AppServices cannot use Self-Signed Certificates, but require a CA …
What is the Shard Map Manager Tool The Sitecore 9 SQL Shard Map Manager sharding deployment tool is designed to create your initial sharded environment that houses raw xConnect data. It’s not intended for rebalancing or reconfiguration of an environment with data. You would need to perform manual steps to reconfigure your environment. The SQL …
If you are using Redis for your Sitecore 9 Private SessionState Provider on Content Delivery Servers and follow the Sitecore documentation for Update 1 located at: https://doc.sitecore.net/sitecore_experience_platform/setting_up_and_maintaining/session_state/session_state/walkthrough_configuring_a_private_session_state_database_using_the_redis_provider, you are likely to experience the following error: StackExchange.Redis.RedisConnectionException: No connection is available to service this operation: EVAL This is because Sitecore’s documentation for the Web.config changes are …
If you have installed Sitecore 9 and attempt to pull up a Sitecore site only to find the following error: “HTTP Error 500.21 – Internal Server Error… bad module “ManagedPipelineHandler” in its module list”, it may because you are missing ASP .NET 4.6 (Sitecore 9 requires 4.6 or 4.7. Please see SIF Prerequisites for more):
To remedy this issue, install ASP.NET 4.6 from the Server Roles manager of Server 2016 or download ASP.NET 4.7
Sitecore 9 XP1 implementations establish two key Windows Services supporting xConnect (that are created as Windows Services via the SIF, but other options exist…. more on that later). These are the Sitecore Marketing Automation Engine and Sitecore XConnect Search Indexer components. Each has distinct responsibilities in ensuring that xConnect properly functions so if xConnect is …
Sitecore 9 brings a heavy paradigm with certificates and intra-machine communication when you decide to implement a scaled XP1 environment. You could have separate servers for each Sitecore role, or an architecture that has xConnect on one Server… CMS, Processing, and Reporting on another… and your CDS(s) serving public traffic. As you need to ensure communication between …
Unweaving the Client Certificates required for an XP1 scaled implementation can be a bit of a challenge, as there are several undocumented steps that need to be undertaken. Often, many will export and import the correct certificates, update connectionStrings to use the proper ThumbPrints, but not update the SSL Settings for the IIS xConnect sites …
Locking down your Content Delivery servers so external users can’t access your content management capabilities and Admin pages is one of the top security steps you need to undertake when deploying a new Sitecore environment. The first step is to implement IP-based security restrictions: Instructions for IIS 7 and greater are as follows: https://docs.microsoft.com/en-us/iis/configuration/system.webServer/security/ipSecurity/ The …
If you are using SIF Version 1.1.0 to generate Self-Signed Certificates and need to export these to other machines as part of a scaled environment, you may find that you are unable to export the Private Keys along with the certificate. In fact, the option to export is grayed out: SIF Version 1.1.0 Created Certificate: …
If you deploy xConnect using the SIF Framework, you will notice a JSON Parameter named “XConnectEnvrionment” with a description of “The configuration environment for this instance” containing a default value of “Development”. “XConnectEnvironment”: { “Type”: “string”, “DefaultValue”: “Development”, “Description”: “The configuration environment for this instance.” }, So, what is the purpose of …