Using Windows Azure AppFabric Service Bus with EPiServer CMS, part 1

This blog post is about registering and calling on-premise services using Windows Azure AppFabric Service Bus from EPiServer CMS. In this series we activate the Service Bus feature of AppFabric, create a WCF REST service, register it on the Service Bus and finally call it from EPiServer CMS.

AppFabric Service Bus

The AppFabric Service Bus provides relay and secure messaging functionality on the Windows Azure platform. A key feature of the Service Bus is the ability to register on-premise services and allow clients to call these services via the Services Bus without actually knowing where or how they are implemented.

servicebusTherefore by leveraging the Service Bus we can create a loosely coupled architecture where key services are exposed to their clients without creating a direct dependency. Since on-premise services automatically register with the Service Bus we do not need to concern ourselves with frequently-changing, dynamically-assigned IP-addresses, or both.


On-premise services communicate with the Service Bus over outbound traffic on port 80. This is a great advantage of using the Service Bus since this requires little or no configuration of firewalls.

EPiServer CMS and AppFabric Service Bus

EPiServer CMS is often deployed on a server provided by a hosting partner that sits outside the company firewall. Consuming data from company on-premise services behind firewalls can therefore be a cumbersome task. We also create a direct dependency to where these on-premise services are deployed.

Register to use the AppFabric Service Bus on the Management Portal

In order to use the AppFabric Service Bus we first need to enable the feature on the Windows Azure Management Portal.

Select Service Bus, Access Control & Caching in the Management Portal.

0.0 Service Bus, Access Control and Caching

Select New Service Namespace.

0.1 Create new service namespace

Configure the Service Bus by giving it a namespace, selecting region and number of connections. For this exercise I’ll be using molniservices.

0.2 Register to use the AppFabric Service

We’re going to be needing values for Issuer and Default Key. Select the newly created namespace and retrieve the Default Key.

0.3 Get owner and key

Copy these and store them for later use.

0.4 Get issuer and shared secret

That’s it! We’re done! In part two we create the on-premise WCF service that we register on the AppFabric Service Bus.

Recent Posts
Contact Us

We're not around right now. But you can send us an email and we'll get back to you, asap.

Not readable? Change text. captcha txt

Start typing and press Enter to search