Skip to main content

Sitecore Azure – Getting up and running

I am a fan of Windows Azure and Sitecore so I figured it was time to see what Sitecore for Azure was all about. The post is just about first impressions and lessons learned while getting started.

There are a few must haves if you are going to work with Sitecore Azure. First you have to get a license file. This is a manual process where you have to email Sitecore with your Sitecore license info and your Azure subscription info (assuming your provisioning your Azure environments yourself). This takes about 24 hours to get the environment file back. Secondly make sure you have the version of the Azure SDK they note in the documentation. In my case it was version 1.7 (documentation gives you a link as well). I figured this was a soft requirement so I just downloaded the latest Azure SDK (1.7 was 2 version behind) however, this did not work and caused deployments to error out (it also gives you an “environment file not found error” in the Sitecore Azure screen).

Once you have all that and you can go into Sitecore – click Sitecore and then click Sitecore Azure you can really start working with it. I first wanted to play with having a local CM (content management) server and a cloud based CD (content delivery) server. So I selected an Azure location and clicked “add delivery farm.” This packaged the current base Sitecore site up and deployed it to Azure.

What is setup for you:

- Azure web role (stagging only. No production role created or started)

- Azure SQL database (core and web). Both setup as Business edition 150GB (I downgraded to Web 1GB for the lower price point and things seem to be working fine still). A UID and PWD is generated for you and the connectionstrings.config file is updated.

- Azure Blob, Table and Queue storage. The following blobs and tables are created for you (no queues are created)


Blob Container Blob Contains Description
CacheClusterConfigs ConfigBlog XML File XML file with ConfigEntries nodes which contain CDATA values
  ConfigSchemaVersionBlob Text File Just a version number
  InitCompleteBlob XML File Empty ConfigInit node
  InitStartedBlog XML File Empty ConfigInit node
Sitecore-auto-deploy     Currently empty
WAD*     Standard Azure WAD blobs


Table Description
WAD* Standard Azure debug and logging tables
$Metrics* Standard Azure metrics tables


- Sitecore publishing target to your Azure web database

What is NOT setup for you: (I was pretty disappointed to see these files are missed and left to the user to flush out)

- GAC level assemblies needed that are not deployed by default. These are assemblies in the GAC that during setup and deployment are not GAC level assemblies Azure hosts (or are different versions) so must be copied to the bin so they are deployed.

- System.Web.WebPages.Razor

- Microsoft.Web.Infrastructure

- System.web.webpages.deployment

- System.Web.Helpers (1.0)

- System.Web.MVC (3.0)

- System.Web.WebPages (1.0)

Once you have copied over the assemblies that are not setup for you, you can now deploy to your Azure environment and hit the site without an error. You will be missing some images because the “/sitecore” directory is not copied over and this is where the default images sit.

As of today Sitecore says this is for Sitecore 6.5 and Azure 2.0. I however did all this with Sitecore 6.6 rev. 130214 and Azure 2.0 rev. 120731 and things seemed to work fine (minus what I noted above, and I doubt that is because 6.6 instead of 6.5).


Shutting Azure down

After this simple test of setting up a content delivery server in Azure I thought I would see what the shutdown process is like. In the Sitecore Azure management window you can click on your node and say suspend. This is pretty easy and does what you would expect and suspends your webrole. Now that the role is suspended lets delete the delivery instance.  In the Sitecore Azure management window the instance looks like it is deleted, but if I look at my Azure account the Cloud Service, databases and storage accounts are still there. Do get rid of these you need to manually delete via the Azure web UI. Not a big deal but disappointing it does not clean itself up better. It also does not clean up any of the environments in the “/sitecore/system/settings/azure/environments” node in Sitecore. Disappointed to see it does not clean itself up better.


Popular posts from this blog

Uniting Testing Expression Predicate with Moq

I recently was setting up a repository in a project with an interface on all repositories that took a predicate. As part of this I needed to mock out this call so I could unit test my code. The vast majority of samples out there for mocking an expression predicate just is It.IsAny<> which is not very helpful as it does not test anything other then verify it got a predicate. What if you actually want to test that you got a certain predicate though? It is actually pretty easy to do but not very straight forward. Here is what you do for the It.IsAny<> approach in case someone is looking for that. this .bindingRepository.Setup(c => c.Get(It.IsAny<Expression<Func<UserBinding, bool >>>())) .Returns( new List<UserBinding>() { defaultBinding }.AsQueryable()); This example just says to always return a collection of UserBindings that contain “defaultBinding” (which is an object I setup previously). Here is what it looks like when you want to pass in an exp

Anatomy of Sitecore Business Rule - Macros

In previous posts, we talked about  field syntax and the basic structure of business rules . This time we are going to dive into macros in the business rules. Macros are used as part of the business rule syntax. The syntax looks like this and calls for 4 parameters. [Property to set, Operator/Macro, AdditionalParameters, Display text]. When I first started working with business rules the difference between operator and macro was confusing. To add to this confusion some of the out-of-the-box macros are named with the term "operator" (like ListOperator who's configuration points to a class called ListMacro and the class implements IRuleMacro). Anything under the path /sitecore/system/Settings/Rules/Definitions/Macros should be a macro and should implement IRuleMacro. Macros have the follow characteristics: They inherit the IRuleMacro interface The interface requires this execute method void Execute(XElement element, string name, UrlString parameters, string value)

Experience Profile Anonymous, Unknown and Known contacts

When you first get started with Sitecore's experience profile the reporting for contacts can cause a little confusion. There are 3 terms that are thrown around, 1) Anonymous 2) Unknown 3) Known. When you read the docs they can bleed into each other a little. First, have a read through the Sitecore tracking documentation to get a feel for what Sitecore is trying to do. There are a couple key things here to first understand: Unless you call " IdentifyAs() " for request the contact is always anonymous.  Tracking of anonymous contacts is off by default.  Even if you call "IdentifyAs()" if you don't set facet values for the contact (like first name and email) the contact will still show up in your experience profile as "unknown" (because it has no facet data to display).  Enabled Anonymous contacts Notice in the picture I have two contacts marked in a red box. Those are my "known" contacts that I called "IdentifyAs"

Excel XIRR and C#

I have spend that last couple days trying to figure out how to run and Excel XIRR function in a C# application. This process has been more painful that I thought it would have been when started. To save others (or myself the pain in the future if I have to do it again) I thought I would right a post about this (as post about XIRR in C# have been hard to come by). Lets start with the easy part first. In order to make this call you need to use the Microsoft.Office.Interop.Excel dll. When you use this dll take note of what version of the dll you are using. If you are using a version less then 12 (at the time of this writing 12 was the highest version) you will not have an XIRR function call. This does not mean you cannot still do XIRR though. As of version 12 (a.k.a Office 2007) the XIRR function is a built in function to Excel. Prior version need an add-in to use this function. Even if you have version 12 of the interop though it does not mean you will be able to use the function. The

Windows Workflow Unit Testing

I know people have very mixed opinions about Windows Workflow and, to be honest, so do I. Really I am not even sure if it has much of a future given the little attention Microsoft has given it. However, despite all that and rather your like it or not there are times when you may use it and want to unit test it. The question is how? Well there are not a lot of options but there is one, that for me, has proven valuable. People tend to use Windows Workflow in a few different ways, so first let me explain how I have use it most. I have never really used it where I programmatically created and instantiate of my own workflow. For me it has pretty much all been using the Windows Workflow designer and using IIS as my workflow host. Then inside those XAML workflows I have custom activities I create and need to test. Do to this I have found one tool that does this pretty well and pretty easy. Microsoft Activities Unit Testing It is an old framework but it still gets the job done. There is