21

Is it needed to use dispatch server in case of using Sitecore Email Cloud? Yes, Sitecore Email Cloud is simply the mail transit provider. You still need dispatch servers to generate the emails and send to the Sitecore EDS service. The process of generating the emails can be taxing based on how complicated your emails are and if personalization rules are ...


10

I don't have an infrastructure diagram, but here is some highlights of the ports you will need to open to establish the communication between Sitecore and the modules/services. WFFM & EXM: The Sitecore will use a SMTP server to send emails, and will depends how the email server is set. The standard port for SMTP is 587. In this case your SMTP server ...


8

It comes down to support. Is there a known reason Sitecore wouldn't work on 2016? No. It will run on 2016 and in all likelihood there will not be any major issues in doing so. But if there is; this is what it comes down to. Let's say you ran into an issue and Sitecore Support was not able to help you out due to it being rooted in something around Server ...


5

You're going to need a more than 10 servers to do 2M hits per second. Assuming each page is 100 hits, you need to serve 20k pages each second. Caching strategies will be critical. MongoDB is going to log gigs each day. IIS logs will be 10's of gigs each day. Disk speed will be critical. Akamai will be needed for all static assets. You need to limit ...


5

Sitecore Publishing Instance is nothing but a clone instance of Sitecore CM environment. On CM server, open \Website\App_Config\Include\Scalability.config file. Update Publish Instance Name as below. <setting name="Publishing.PublishingInstance"> <patch:attribute name="value">PI-Sitecore</patch:attribute> </setting> If ...


4

Azure PaaS on the Cheap Your focus seems to be on reducing costs, so the first thing to make sure of is to reduce the number of app service plans being used. This doesn't necessarily mean merging together apps in Sitecore, but making sure your apps use the same app service plans. There are some examples of this in the standard topologies. Note how Small and ...


3

From your question what I understand is that you want a kind of blue-green migration of Solr into SolrCloud. I will suggest you, perform a rebuild index so that you will have everything thing new in SolrCloud, and it also ensures that there are no index rebuild errors after migration. Now how we can perform this with 0 downtimes? We need to switch the Solr ...


3

If you have setup 2 CM servers, both will be able to publish. So you need to make sure that they only publish their own jobs. As SitecoreClimber mentioned, you can use the Publishing.PublishingInstance setting for this. If you look at the ScaleabilitySettings.config.example file included in your Sitecore installation it says this: <!-- PUBLISHING ...


2

Sitecore 8.2 Update 3 does support Windows Server 2016. https://kb.sitecore.net/articles/087164 In the operation systems table, Windows Server 2016 is checked under 8.2 and links to the following note: "[21] Compatible beginning with Sitecore XP 8.2 Update-3."


2

If you are not planning on using marketing automation, you might want to setup an XM environment. XM is sitecore CMS-only and doesn't include xDB. https://doc.sitecore.net/sitecore_experience_platform/setting_up_and_maintaining/experience_management/experience_management_an_overview In this setup, you don't need those xDB services and only require a CM and ...


1

We recently migrated our existing Solr to Solr cloud on the Prod environments. We followed a similar kind of approach suggested by Mahendra. We first migrated the Solr to Solr Cloud on the CM by making the connection string changes, config changes and did the indexing, while the indexing is performing in the background the CD server still serves the data ...


1

It looks like the Reporting role is configured incorrectly out of the box. It does not have the Reference Data subsystem enabled. Here's how you can fix this. Step 1 Open the file Sitecore.Xdb.ReferenceData.Service.config located under \App_Config\Sitecore\Marketing.Xdb.ReferenceData.Service\ Update <sitecore role:require="Processing or Standalone"> ...


1

you can run all the services in one of the other roles - so minimum need without discussing what the performance requiresments of the site it should run is difficult. You can just move all webroles to the same app service plan for cost savings - it is the app service plan that has the real cost. Do not forget the infrastructure services (Redis cache and ...


1

Load of each Sitecore implementation is unique depending on how it is designed, caching, components, etc.. This question is also opinion based, IMHO. However, I do want to advice you to reach out to your regional Sitecore sales rep. in addition to Sitecore support, which you already have! You will also need to take into consideration your licensing model. ...


1

I can confirm that such approach can be really useful from our experiences. We are using a quite huge infrastructure set-up for our solution: like five independent clusters, every cluster contain one CM for editors and another CM for publishing (+ other service jobs). There is even one global admin (CM) from where the contents are regularly distributed into ...


Only top voted, non community-wiki answers of a minimum length are eligible