Damir Dobric Posts : AppFabric

Power of Windows Azure PaaS: State Share and Persistence in the cloud

Damir Dobric — Mon, 22 Apr 2013 13:00:00 GMT

If you are experienced enterprise developer who targets the Microsoft platform, you have probably at least once in your have a requirement to share some state across different instance of an application.
But, if you are hobby developer or any other professional developer, who possible do not focus distributed systems, you will might find the term “State” in context of persistence a pure theory thing.
So who ever you are, let’s start with a simple theory thing.
Imaging you have in theory a trivial application (today I call such applications simply “apps”). Assume this is an app running on smart phone or any other mobile device. This app has a variable ‘A’ and value assigned to this variable ‘1’. This value is not the default value. It is rather the value which user has assigned at some point of time.

Now, imagine the application crashes and you start it again. The value of variable A is obviously lost. If you want to keep this value somewhere, so it can be loaded even if application crashes. We call that usually persistence. Depending on application and your skill, there are several ways to persists the value of an variable. For example you can use any kind of local cache, like a file system.

But what if your application has to survive the hardware damage? Or what if your application is consisted multiple clients which have to share the same value? In this case you will have to use some kind of database.
As long you are in control of your infrastructure (means application is deployed in your enterprise) you can use some database to persist the value. The good example of this is Workflow Foundation. Long running processes require by default the state persistence.
Unfortunately we have more often scenarios where applications are distributed across the web. In such cases the only sharing artifact between such applications is the cloud. Following picture shows how two apps (or applications) share their state through the cloud.

This is a nice theoretical case which is practically a horror to implement. I strongly believe that today we are implicitly preparing for dominance of devices in the web. In this hypothetical scenario both devices (see picture above) should act as services to be able to share their state. If you are distributed application or integration developer you know that connectivity us such scenarios is a big, big issue. Or simply, it is the fact, devices in the web have a private IP address and because of that they are not reachable by anybody. So if the microscope on the left cannot reach the smart-phone on the right, the state from left to right cannot be propagated and vice versa.

If this to theoretical to you, imagine just a service which is running distributed across cloud. This might be WCF service, Windows Service (running in SCM) or even Web Api based service. Whatever technology you peek, it does not matter. The only important thing is that you want run multiple instances of the service, but on two machines which are not in the same environment (if they are in the same environment even better). So that means, independent on a case, devices or services or both, we have the same requirement:

1. Sharing of the state between applications distributed in the web
2. Persisting of the state without database.

You believe or not, this problem can be solved by using Windows Azure Service Bus, which in this case plays a role of cloud artifact. To illustrate how this can work, take a look on following example.
This is a console application in C#. The state which should be shared and persisted across many applications is stared in variable State.

class Program{

public static WebState<string> State { get; set; }

static void Main(string[] args)
{

State = new WebState<string>(ConfigurationManager.AppSettings["SbConnStr"], "BusinessDomain", ConfigurationManager.AppSettings["Node"]);

           State.StateChanged += State_StateChanged;

            Console.WriteLine("I'm node with name: " + ConfigurationManager.AppSettings["Node"]);

Console.WriteLine("Running with state: {0}", State.Value);

           while (true)
            {
                State.Value = Console.ReadLine();
            }
        }

        static void State_StateChanged(object sender, WebStateEventArg<string> e)
        {
            Console.WriteLine("State changed by {0} at value: {1}", e.InstanceName, e.NewValue);
        }

}

As you see this variable is of type WebState, which is implemented by me. When you start this application, enter some text on the console. The text will be immediately persisted in the cloud after following line of code is executed:

State.Value = …

Now stop the application gracefully and start it again. You will notice that application write out the value which was as last one persisted. In fact event with one participant in the system you have achieved the persistence.
The magic behind this is implemented on top of Windows Azure Service Bus queues. Each time the value is changed, the WebState implementation receives the existing message from the queue and put back the new message in the queue which basically holds the serialized value of variable State, and so on. Because access to the queue is session based, Service Bus guaranties that no any other applications which shares this value, will access the queue in the same time. I don’t want to call this distributed transaction, but it behaves in persistence this scenario like it would be one. In fact the WebState class uses the Queue as a unit of storage. By reading and immediate writing back of the new value, it is guarantied that the queue holds one and only one message all the time.
Following picture illustrate this. Each time the value i changed the old value is stored in the queue as a message. The old value is received from queue and the new message with new value is sent to the queue. At the end the old one is completed, because PeekAndLock receive is used.When the new instance of the State is created (for example when application is started) the same cycle with receive/send is done. This is how multiple applications obtain there actual state.

Additionally the implementation of the WebState takes a care about state sharing. For this purpose there is a topic used to share state changes. All participants in this distributed system have to create a subscription on that topic.
In this case (see picture below) the new value is published as a message to the topic. After that all subscribers can receive the message with the new value. The publishing process additionally updates the new value in the persistence queue from previous example.

Because topic-subscriptions are used, the application which was not running for a while, will automatically receive all state changes which have happened in the mean time.

This examples shows how complex patterns can be implemented by using connectivity service in Windows Azure. I know that majority of people out there still think a..bout cloud as an old thing. There is also a group of people who thinks that cloud is unsafe think to keep the data. If you are one them them please rethink your thinking. The scenario and solution shown above is a new way of thinking and using cloud services. And the nice think here is that practically no real data is stored in the cloud.
As you see, the cloud is more than solely putting of some application online. :)

The code for this will be published soon.

ExpressionTranslator Error when publishing Workflows

Damir Dobric — Tue, 26 Mar 2013 21:43:00 GMT

When working with Workflows, which running in Workflow Manager (SP devs call it usually SharePoint Workflow) on-premises or in Office 365 you might get following error:

Expression: DateTime.Now.ToString()

"Property access conversion to an activity is not supported for property 'CurrentDomain' defined on type 'System.AppDomain'."

This error occurs during Translation of the workflow. The translation is a step in process of publishing of the Workflow in Workflow Manager. it basically translates all expressions in Workflow Activities in a form
required by XAML, before the workflow is published (installed) to the host.

Following picture shows an expression which will cause described error:

The picture left below shows XAML expression which is translated in a bit different expression (picture right below). Note that DateTime.Now.ToString() is in this case not evaluated. It is a pure string like “BLA, BLA”.

   <Assign sap2010:WorkflowViewState.IdRef="Assign_1">
      <Assign.To>
        <OutArgument x:TypeArguments="x:String">
          <mca:CSharpReference
            x:TypeArguments="x:String">result</mca:CSharpReference>
        </OutArgument>
      </Assign.To>

      <Assign.Value>
        <InArgument
         x:TypeArguments="x:String">DateTime.Now.ToString()
        </InArgument>

</Assign.Value>

</Assign>

Right now, it is not possible to access properties within Expressions. To make this working you will unfortunately have to define the type to access properties. For example, if you want to access MyCustomTye.MyProp you will have to create the activity like GetMyCustomPropActivity and define InArgument<MyCustomTye> and OutArgument<yourproptrustedtype>. The later one will hold the value of MyProp.
This activity have to extend trusted surface (se URL below) even if the type is common .NET type like DateTime.

How to create custom activities:

http://developers.de/blogs/damir_dobric/archive/2012/09/16/workflow-trusted-surface.aspx

http://msdn.microsoft.com/en-us/library/windowsazure/jj193517(v=azure.10).aspx

How to setup Service Bus permission ?

Damir Dobric — Tue, 04 Dec 2012 15:21:00 GMT

When working with ServiceBus for Server, the setup is responsible to define default user’s permissions. During setup procedure you will have to provide the credentials of the user who will be admitted to host and to manage Service Bus.
However permissions for Workflow Manager are managed a different way. During installation of the Workflow Manager you will have to provide the name of the group of users (by default BUILIN\Administrators) who can manage the Workflow Host.
This will setup the permissions for user who can manage Workflow Host. But note this will not setup permissions for Service Bus namespace. This is so far not a limitation, because in a case of Workflow Host you will usually not deal with Service Bus Namespace directly. Even more the namespace behind Workflow Host is more or less a hidden artifact.
But sometimes there are scenarios especially with ServiceBus in play, which enable you to do powerful things by dealing directly with Service Bus. You can this way extend the functionality of the Workflow Host. This might be in the future a valid and possibly lovely scenario for SharePoint developers.

If so, you will have to change permissions of the namespace of the Workflow Host in the Service Bus itself.Before you start type Get-SBNamespace WorkflowDefaultNamspace. This Power shell command shows the current state of the default namespace assuming this is the namespace which you want to manipulate).

Name                  : WorkflowDefaultNamespace
AddressingScheme      : Path
CreatedTime          : 11/28/2011 1:56:25 PM
IssuerName            : WorkflowDefaultNamespace
IssuerUri                : WorkflowDefaultNamespace
ManageUsers           : {appfabriuser@daenetlab.lan, bahro@daenetlab.lan}
DnsEntry              :
PrimarySymmetricKey   : ABC…DEF..OBFUSCATED=
SecondarySymmetricKey :

As you see there are two users permitted to manage the namespace. appfabricuser and bahro. Both are from the same domain daenetlab.lan.
If you want to extend permission to additional user (i.e. damir) do following:

PS C:\Program Files\Workflow Manager\1.0> set-sbnamespace -ManageUsers appfabr
csuser@daenetlab.lan, bahro@daenetlab.lan, damir@daenetlab.lan

Execute Get-Namespace again and here we are:

Name                  : WorkflowDefaultNamespace
AddressingScheme      : Path
CreatedTime          : 11/28/2011 1:56:25 PM
IssuerName            : WorkflowDefaultNamespace
IssuerUri                : WorkflowDefaultNamespace
ManageUsers           : {appfabriuser@daenetlab.lan, bahro@daenetlab.lan, damir@daenetlab.lan}
DnsEntry              :
PrimarySymmetricKey   : ABC…DEF..OBFUSCATED=
SecondarySymmetricKey :

New user has been added and this namespace can be used now for custom extended scenarios on top of your already used namespace.

Agenda for SharePoint Workflow Engine Deep Dive

Damir Dobric — Sun, 18 Nov 2012 21:05:01 GMT

Announcing agenda for session “SharePoint Workflow Engine Deep Dive” at conference “Knowledge Days rund um SharePoint - DAS Event zu Microsoft SharePoint 2013” in Munic at
Nov. 20 and Nov.21. 2012.

AGENDA

Serialization of Exceptions in Workflow Manager

Damir Dobric — Fri, 16 Nov 2012 21:03:00 GMT

Note that when using workflows with Variables of type Exception, you might run into serialization issues. This is usually not a general Workflow problem. However if you use persistence feature, workflow host with enforce serialization of all variables in the workflow. Because Exception is not by default a serializable type, the workflow will fail in the moment of serialization.

The things are getting even worse if you use Workflow Manager as a host. For all of you SharePoint developers, this is always the problem, because SharePoint Workflows are by default serializable.

Here is what you can do before activity which cause the workflow to be persisted:

Workflow is persisted when Persists activity, Delay Activity or any other listener (wait on message) activity is started and the host is Workflow Manager.
In a case of AppFabric server as host, things looks a bit different.

Announcing my Session “Connecting Web Systems” at Advanced Developer Conference 2012

Damir Dobric — Sat, 27 Oct 2012 12:45:15 GMT

If you are professional developer or architect who focus Microsoft technologies, then ADC is the conference of great choice. Internationally recognized and legendary experts will present most popular technology topics.
One of best things at this conference I personally like is “NO MARKETING”. All session content is pure experience with pre-filtered sponsoring and marketing noise.

At the upcoming Advanced Developer Conference 2012 in Germany I will give two session. Here is the first look on agenda for “Connecting Web Systems” session. Because this session is not related to some product, it will focus new peaces of technology at the Microsoft’s development platform. This time I decided to talk about technologies which might dramatically change the web soon. However this might also influence the way how we thing about applications and it will definitely change the architecture of future applications. As Integration MVP in last two years I was involved in some more or less hidden and still not well documented technology areas with focus on WebSockets, SignalR and communication in Web in general.
Content presented in this session is pure result of this work. You are welcome.

Windows Server AppFabric HotFixes

Damir Dobric — Fri, 19 Oct 2012 20:22:49 GMT

Cumulative HotFixes for Windows Server AppFabric:

http://msdn.microsoft.com/en-us/library/hh351221.aspx

How to activate WCF on IIS8 and Windows 8?

Damir Dobric — Mon, 24 Sep 2012 15:03:18 GMT

When you start working with WCF on Windows 8 and IIS8, you might run into following problem.

HTTP Error 404.3 - Not Found

The page you are requesting cannot be served because of the extension configuration. If the page is a script, add a handler. If the file should be downloaded, add a MIME map.

To make this working you have enable (install/activate) Advanced .NET 4.5 Features, which are mostly related to WCF:

ServiceBus Message Broker Service is starting and starting…(Cannot Deploy SPS Workflow)

Damir Dobric — Tue, 18 Sep 2012 05:21:00 GMT

When working with Windows Azure Workflow, Workflow Host Manager or Share Point 2013 Workflow you might experience several problems related to Message Broker Service.

Issues related to broker In SharePoint are manifested through workflow deployment issues. For example, if you try to deploy the workflow you might get following error:

Error 1 Error occurred in deployment step 'Activate Features': System.IO.InvalidDataException: A response was returned that did not come from the workflow service. Status code = 503:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd">
<HTML><HEAD><TITLE>Service Unavailable</TITLE>
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD>
<BODY><h2>Service Unavailable</h2>
<hr><p>HTTP Error 503. The service is unavailable.</p>

If you are rather Service Bus guy, you will figure out that Broker Service does not start. It is all the time in starting status. In both cases, take a look on status of Windows Fabric Host Service. You will probably notice that this service is not running. If so start it, stop the broker and start the broker again.
If you cannot stop the broker service while starting, got to task manager and kill Microsoft.ServiceBus Message Broker process. Then start the broker service.

Workflow Expression Error: Left and Right argument types should match for comparison operations

Damir Dobric — Mon, 20 Aug 2012 10:24:16 GMT

When building custom workflows in SharePoint or when building in general Workflows with WF 4.5, you might get following error:

”Left and Right argument types should match for comparison operations”

Due the new C# Expression support, this error will happen if you have an C# expression like shown at the next picture:

To workaround this, change expression as follows:

Is Service Bus Server an ESB product?

Damir Dobric — Wed, 01 Aug 2012 06:23:00 GMT

Service Bus 1.0 (also called Service Bus Server) is a Microsoft messaging product, which many people will compare with Enterprise Service Bus. Currently Microsoft is NOT positioning Service Bus Server as an ESB product. The reason for that is that Service Bus doesn’t support many of features which are supported by typical ESB. For example a common service bus supports features like We don’t have any of the ‘other’ ESB features like: protocol conversion, message transformation, adapters (in term of BizTalk), business monitoring etc.

Service Bus is for now a messaging runtime focused on rich messaging patterns like pub-sub & queues. Moreover it guaranties on-prem and cloud symmetry.

To recap, Service Bus is not an ESB product but rather a messaging platform.

An interesting combination of Service Bus Server and Workflow enables however easy implementation of highly scalable workflow based and long running scenarios, which make place for new innovative solutions.

For more information take a look here.

Installing Workflow 1.0 BETA with Workflow Host

Damir Dobric — Tue, 31 Jul 2012 07:34:36 GMT

First of all download all components from http://www.microsoft.com/en-us/download/details.aspx?id=30369 To install the Service Bus run workflow.3f.3f.3fnew.exe.
Another possibility would be to use Web Platform installer.

After start of installation setup will detect dependent components. Please note that restart will be required assuming that .NET 4.5 has not been previously installed. It is important to understand that Workflow Host has a dependency to Service Bus.

If you previously didn’t install Service Bus you can proceed with installation of Workflow Manager directly. Setup will automatically recognize missing dependencies.

Click I Accept to proceed. Please also note that Workflow used in Workflow 1.0 BETA (the name might be changed future) is built on top of .NET 4.5. This means that this version of Workflow is almost identical with the common WF 4.5. This Workflow BETA 1 contains few more activities which support activation of workflow instances via service bus message. Moreover, current version does not support Messaging activities like ReceiveMessage. This is an important architecture issue you should be aware of!

After installation of .NET 4.5 you will have to restart the machine.

At the end following appears:

After all Workflow will appear in start menu:

Last but not least, do not forget to install Workflow Tools for Visual Studio.

If you don’t install them new activities will not appear in designer and design time APIs cannot be uses (i.e. publishing of workflow).

Installing Service Bus Server 1.0 BETA

Damir Dobric — Tue, 24 Jul 2012 13:35:00 GMT

In July 2012 Microsoft has for the first time published a peace of Windows Azure which is installable locally (On-Premise). It is Service Bus (v1 BETA) which is slightly adapted version of Windows Azure Service Bus. If you are aware of this product this post will help you to install it. If you are new to Service Bus Server (this is how some people call it) it is highly recommended to take a look on this article.

Before you start with installation go to following URL and download all required components from http://www.microsoft.com/en-us/download/details.aspx?id=30376. To install the Service Bus run servicebus.3f.3f.3fnew.exe. Another option to do that is to use Web Platform installer v4. Following picture shows two new components in Platform Installer. This post is related to installation of Service Bus 1.0. If you want to install Workflow 1.0 you will anyhow have to first install Service Bus.

After start of Service Bus Server setup following dialog appears:

Immediately after start the list of missing dependencies will appear (see picture below). Please note that after installation restart will be required! Note that if you previously have installed Windows Fabric component you will have to uninstall it. Note that it is not necessary to go to direct link (shown below). Simply click "I Accept" to proceed. Setup will automatically download and install required components.

After installation of Service management Components 3.0 you will have to restart the machine.

After restart the installation will proceed automatically. At the end the start menu will contain the node “Windows Azure Service Bus” :

How to uninstall Service Bus Server and Workflow Host?

Damir Dobric — Thu, 19 Jul 2012 05:42:00 GMT

This post is related to BETA version of Service Bus Server and Workflow Host which is used in Share Point 2013. It should help you to uninstall previous version of Service Bus and Workflow.

Use the following procedure to remove Workflow and Service Bus from a node in a farm. You must perform these actions on every node from which you want to delete Workflow and Service Bus.

1. Go to stare menu locate AppFabric Server and start configuration wizard. Remove the node from the farm as described in "Leaving a Farm". If you have lot of time you can also use PowerShell.

2. Open the Control Panel windows and uninstall following components:

Microsoft AppFabric

Microsoft Windows Fabric

After these steps ServiceBus and Workflow including Windows Azure Fabric which is running locally are removed. However all databases will remain at the SQL server. If you want to remove them, you can/should first make a backup.

You can use SQL Management Studio to remove the databases that were associated with Workflow and Service Bus.
Following databases are related to SB and WF Host:

a. AppFabricManagementDB

b. SbGatewayDatabase

c. SBContainer01

d. WFInstanceManagementDB

Last but not least. if you have Visual Studio installed at the machine and have previously installed Workflow Client, you will have to remove it too. If you don’t do it the installation of the new Workflow Client and Workflow itself will fail.

Hello Service Bus 1.0, Workflow 1.0 and SharePoint Workflow Host

Damir Dobric — Tue, 17 Jul 2012 04:08:18 GMT

The OnPrem version of Windows Azure Service Bus is probably firs peace of Azure Cloud which can be installed on your laptop. Personally I would call it Enterprise Service Bus, which can and should be used for almost any kind of messaging in enterprise. The good thin on this is that the exactly (more or less) the same version is running in the Windows Azure Cloud. The exactly same means in term of API which developers will used. “More or less” means that there are still few differences.
First and probably less important difference is Relaying feature. This feature is currently supported in the cloud only (at least for now). Queue and Topic messaging is fully supported.

Windows Token

However from the architecture point of view, it is more important that On-Premise version (Service Bus Server) additionally to ACS use Windows Token to access queues and topics. To make this working, SB supports internally some kind of Security Token Service, which is able to issue the ACS compatible token on behalf of Windows Token tight in the first message request.
This is all you should now for now about this STS. In fact it is transparent for developer and you shouldn’t eve know that it exist. This information is interesting to understand that there is no any magic behind changed security system. Please note that Service Bus Server can also create a namespace in SB which uses ACS just like SB in azure.

Service Bus Configuration in PowerShell

The currently available release supports Power Shell Based configuration only. The RTM version will additionally support a Configuration Wizard.
Note the Service Bus Explorer supports Service Bus Server (see link below).

Installation via WEB PI 4

Currently you will have to use WEB Platform Installer v4 http://www.microsoft.com/web/downloads/platform.aspx. to install the bits. The setup contains in fact two products: Windows Azure Workflow and Service Bus. Both products are installable on your machine. Yes, that’s right. Windows Azure Workflow is installable on the local machine. Depending on what you want to install, select SB or/and WF and proceed with installation.

Topology Facts

The SB cluster is supported with High Availability feature similar to caching service. That means HA is supported by 3+ nodes in the cluster.
The underlying database can be SQL Express (no joke), SQL 2008 and even SQL 2012.
Workgroups are supported too.
Up to now, bits can be installed on Windows 7 and Windows 8 client OS family. Both are currently supported for development purposes only.

Workflow 1.0

The workflow version installed here needs much more space and time to be explained. For now it is important that you can run your Workflows in Windows Azure. The same version can also be run on-premise. Unfortunately this version cannot use Windows Server AppFabric. The team has internally decided to build the new host for massive scale which activates Workflow Instances from Service Bus topic. At the moment you will have decide whether to use the Windows Server AppFabric host or this one. The new host has been specifically built for SharePoint 15 which is first Microsoft product which will span its workflows on top of Service Bus on premise.
Note that the same host and workflow will be used by SharePoint Online Version.
With this version SharePoint has finally a serious host for running processes outside of SPS pool. My best wishes.(I was waiting almost 10 years for this). More experienced architects and developers might start to think about SharePoint as a SAP Netweaver. Please just don’t overuse it in this case (as often in the past of SPS).
Authoring of Workflows and SPS13 Workflows is WF 4.5.
NOTE, that not all activities of the common WF 4.5 version are supported. For example messaging activities (i.e. ReceiceMessage) and versioning are not supported. Fortunately there are special activities which can perform activation of workflow by message. In fact this is the only way to start he workflow.
If you want to use custom activities in On-Prem version of workflow, there are few extra steps which you have to manually (for now) perform.

Following sample illustrate how to receive the message from topic.

using System;
using System.Collections.Generic;
using System.Net;
using Microsoft.ServiceBus;
using Microsoft.ServiceBus.Description;
using Microsoft.ServiceBus.Messaging;

namespace Daenet.ServiceBus
{

    public class Subscriber
    {
        private static string ServiceNamespace;
        private static string Issuer;
        private static string Key;
        private static string TopicName = "demotopic";


        static void Main(string[] args)
        {
            ServicePointManager.ServerCertificateValidationCallback = (a, b, c, d) =>
            {
                return true;
            };

            Uri rootAddressManagement =
            ServiceBusEnvironment.CreatePathBasedServiceUri("https",
             “testspace01”, string.Format("{0}:{1}", "YOURHOST", 4446));

            Uri rootAddressRuntime = ServiceBusEnvironment.CreatePathBasedServiceUri("sb",
               “testspace01”, string.Format("{0}:{1}", "YOURHOST", 9354));

            NamespaceManagerSettings nmSettings = new NamespaceManagerSettings();
            nmSettings.TokenProvider = TokenProvider.CreateWindowsTokenProvider(new List<Uri>() { rootAddressManagement });
            NamespaceManager namespaceManager = new NamespaceManager(rootAddressManagement, nmSettings);

            MessagingFactorySettings mfSettings = new MessagingFactorySettings();
            mfSettings.TokenProvider = TokenProvider.CreateWindowsTokenProvider(new List<Uri>() { rootAddressManagement });
            MessagingFactory factory = MessagingFactory.Create(rootAddressRuntime, mfSettings);

            SubscriptionClient subscriptionClient =
            factory.CreateSubscriptionClient(TopicName, "Subscription1", ReceiveMode.PeekLock);

            while (true)
            {
                BrokeredMessage message = subscriptionClient.Receive(TimeSpan.FromSeconds(1500));
                if (message == null)
                    break;

                try
                {
                    Console.WriteLine(string.Format("Message received: SEQUENCE = {0}, Id = {1},
                    Body = {1}", message.Properties["SEQUENCE"], message.MessageId, message.GetBody<string>()));
                    message.Complete();
                }
                catch
                {
                    message.Abandon();
                }
            }

            Console.WriteLine("\nEnd of receiving, press any key to exit.");
            Console.ReadLine();

            subscriptionClient.Close();
        }
    }
}

It is important in this sample that things like Issuer and Key are not required. The scope used by issuing of the token is like

scope=http%3a%2f%2yourhostname%2ftestspace01%2fdemotopic%2fSubscriptions%2fSubscription1.

The issued token is is private for developers and it will be passed internally to all calls to service bus. On thing of your interest is that this token contains claims which describe users AD membership. Based on this information SB will perform authorization.

Resources:

Service Bus Beta resources:

Service Bus 1.0 Beta (download)

Service Bus for Windows Server (Service Bus 1.0 Beta) MSDN documentation

Service Bus Explorer for Windows Server

Workflow 1.0 Beta resources

Workflow 1.0 Beta (download)

Workflow 1.0 Beta MSDN Documentation

Enjoy