<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>arm on bramstoop.com</title>
    <link>https://www.bramstoop.com/categories/arm/</link>
    <description>Recent content in arm on bramstoop.com</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Thu, 06 Aug 2020 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.bramstoop.com/categories/arm/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Setup Solr cluster with Zookeeper ensemble on Windows</title>
      <link>https://www.bramstoop.com/posts/2020/08/2020-08-06-setup-solr75-cluster-with-zookeeper-ensemble-on-windows/</link>
      <pubDate>Thu, 06 Aug 2020 00:00:00 +0000</pubDate>
      
      <guid>https://www.bramstoop.com/posts/2020/08/2020-08-06-setup-solr75-cluster-with-zookeeper-ensemble-on-windows/</guid>
      <description>BACK TO BLOG OVERVIEW
 Within this post I will show you how to setup a Solr cluster with a Zookeeper ensemble while load being distributed by an Azure loadbalancer.
Note: There is no SSL used and in the future the Azure loadbalancer might get replaced by an Application Gateway.
I would like to thank the owners (amongst others, I probably missed) of the following blogs for being a more than valuable source of information:</description>
    </item>
    
    <item>
      <title>Sitecore Identity server deployment: &#34;AspNetCoreRuntime extension not found&#34;</title>
      <link>https://www.bramstoop.com/posts/2019/09/2019-09-19-sitecore-identity-server-deployment/</link>
      <pubDate>Thu, 19 Sep 2019 00:00:00 +0000</pubDate>
      
      <guid>https://www.bramstoop.com/posts/2019/09/2019-09-19-sitecore-identity-server-deployment/</guid>
      <description>BACK TO BLOG OVERVIEW
 When you run in to the following ERROR while deploying your Sitecore XP solution, and in specific the Identity Server:
8:21:15 PM - Resource Microsoft.Web/sites/siteextensions &amp;lsquo;xxx/AspNetCoreRuntime&amp;rsquo; failed with message &amp;lsquo;{
&amp;ldquo;id&amp;rdquo;: &amp;ldquo;/subscriptions/xxx/resourcegroups/xxx/providers/Microsoft.Web/sites/xxx/siteextensions/AspNetCoreRuntime&amp;rdquo;,
&amp;ldquo;name&amp;rdquo;: &amp;ldquo;xxx/AspNetCoreRuntime&amp;rdquo;,
&amp;ldquo;type&amp;rdquo;: &amp;ldquo;Microsoft.Web/sites/siteextensions&amp;rdquo;,
&amp;ldquo;location&amp;rdquo;: &amp;ldquo;West Europe&amp;rdquo;,
&amp;ldquo;properties&amp;rdquo;: {
&amp;ldquo;id&amp;rdquo;: &amp;ldquo;AspNetCoreRuntime&amp;rdquo;,
&amp;ldquo;title&amp;rdquo;: null,
&amp;ldquo;type&amp;rdquo;: &amp;ldquo;Gallery&amp;rdquo;,
&amp;ldquo;summary&amp;rdquo;: null,
&amp;ldquo;description&amp;rdquo;: null,
&amp;ldquo;version&amp;rdquo;: null,
&amp;ldquo;extension_url&amp;rdquo;: null,
&amp;ldquo;project_url&amp;rdquo;: null,
&amp;ldquo;icon_url&amp;rdquo;: null,
&amp;ldquo;license_url&amp;rdquo;: null,
&amp;ldquo;feed_url&amp;rdquo;: null,
&amp;ldquo;authors&amp;rdquo;: null,</description>
    </item>
    
    <item>
      <title>Validate (all) your Sitecore ARM templates on build</title>
      <link>https://www.bramstoop.com/posts/2019/05/2019-05-16-validate-all-your-sitecore-arm-templates-on-build/</link>
      <pubDate>Thu, 16 May 2019 00:00:00 +0000</pubDate>
      
      <guid>https://www.bramstoop.com/posts/2019/05/2019-05-16-validate-all-your-sitecore-arm-templates-on-build/</guid>
      <description>BACK TO BLOG OVERVIEW
 While working with ARM templates and Azure DevOps it definitely adds value to validate all your Json files during build. This might save you a lot of time. To implement this you could setup the following tasks within your build pipeline:
Add a &amp;lsquo;npm&amp;rsquo; task within your build and configure it as below:
Now add a subsequent Powershell task, run it inline and add the following script:</description>
    </item>
    
    <item>
      <title>Baseline your Sitecore dashboards using ARM templates</title>
      <link>https://www.bramstoop.com/posts/2018/10/2018-10-18-baseline-your-dashboards-using-arm-templates/</link>
      <pubDate>Thu, 18 Oct 2018 00:00:00 +0000</pubDate>
      
      <guid>https://www.bramstoop.com/posts/2018/10/2018-10-18-baseline-your-dashboards-using-arm-templates/</guid>
      <description>BACK TO BLOG OVERVIEW
 In one of my previous posts (click) I mentioned some useful AI query&amp;rsquo;s for maintaining and managing your Sitecore solution. To make sure every Sitecore solution(s) you are managing will be deployed with a baseline dashboard I added all the query&amp;rsquo;s to an ARM template. 
1.Download the arm template:
[code language=&amp;quot;powershell&amp;rdquo;] $url = &amp;ldquo;https://raw.githubusercontent.com/bstoop-github/public/master/Sitecore/dashboard/deployDashboard.json&amp;quot; $output = &amp;ldquo;c:\TMP\deployDashboard.json&amp;rdquo;
Invoke-WebRequest -Uri $url -OutFile $output [/code]</description>
    </item>
    
    <item>
      <title>Sitecore Symposium 2018 - Must read takeaways!</title>
      <link>https://www.bramstoop.com/posts/2018/10/2018-10-16-sitecore-symposium-must-read-takeaways/</link>
      <pubDate>Tue, 16 Oct 2018 00:00:00 +0000</pubDate>
      
      <guid>https://www.bramstoop.com/posts/2018/10/2018-10-16-sitecore-symposium-must-read-takeaways/</guid>
      <description>BACK TO BLOG OVERVIEW
 &amp;ldquo;Returning from this year&amp;rsquo;s Sitecore Symposium in Orlando, I would like to share some improved/new insights that have come to me due to attending some great sessions. Some of this blog post will assume you are using a Sitecore on Azure PAAS solution. Most sessions I attended were related to continuous integration, continuous deployment, architectures, scaling, high availability and disaster recovery. The sessions from Bas Lijten, Dennis Weston and Rob Habraken inspired me most and therefore I will elaborate/reflect on most of their content.</description>
    </item>
    
    <item>
      <title>Appsettings not present after ARM deployment</title>
      <link>https://www.bramstoop.com/posts/2018/03/2018-03-27-appsettings-not-present-after-arm-deployment/</link>
      <pubDate>Tue, 27 Mar 2018 00:00:00 +0000</pubDate>
      
      <guid>https://www.bramstoop.com/posts/2018/03/2018-03-27-appsettings-not-present-after-arm-deployment/</guid>
      <description>BACK TO BLOG OVERVIEW
  Within the config section of an App Service you are able to define multiple sections. In this example we are using three sections : web, appsettings and logs.
Since we noticed that sometimes the expected settings were not configured/missing after a deployment we figured out some missing dependsOn settings need to be set.
Please note that in the ARM snippet below the appsettings depend on the web settings to be processed.</description>
    </item>
    
    <item>
      <title>Sitecore 9.0.1 - xcServerConfigurationEnvironment parameter</title>
      <link>https://www.bramstoop.com/posts/2018/03/2018-03-16-sitecore-9-0-1-xcserverconfigurationenvironment-parameter/</link>
      <pubDate>Fri, 16 Mar 2018 00:00:00 +0000</pubDate>
      
      <guid>https://www.bramstoop.com/posts/2018/03/2018-03-16-sitecore-9-0-1-xcserverconfigurationenvironment-parameter/</guid>
      <description>BACK TO BLOG OVERVIEW
 We&amp;rsquo;re setting up an automated deployment using the Sitecore ARM templates. Doing so we came across the following parameter: xcServerConfigurationEnvironment This variable can contain either &amp;ldquo;Development&amp;rdquo; or &amp;ldquo;Production&amp;rdquo; and is used in the x-connect and Marketing automation apps. We were wondering what the purpose of this variable is and how this parameter should be configured on the different environments?
Answer:
I would like to address your question regarding the &amp;ldquo;xcServerConfigurationEnvironment&amp;rdquo; parameter.</description>
    </item>
    
  </channel>
</rss>