Mick's Breeze Blogs - Biztalk/Sharepoint/... - AppFabricServer

Azure ServiceBus: Fixing the dreaded ‘The X.509 certificate CN=servicebus.windows.net chain building failed’ error

Mick Badran — Tue, 31 Jan 2012 03:08:41 GMT

Scotty & myself have had this error going for over 2 weeks now, and have tried many options, settings, registry keys, reboots and so on.
(we have had this on 2 boxes now, that are *not* directly connected to the internet. They are locked down servers with only required services accessible through the firewall)

Generally you’ll encounter this error is you install Azure SDK v1.6 – there has been people that have revert back to Azure v1.5 SDK when this error has been encountered and this seems to fix most of their problems.

Here I’m using netTcpRelayBinding, BizTalk 2010 but this could just have easily have been IIS or your own app.

Finding the outbound ports and Azure datacenter address space is always the challenge. Ports 80,443,9351 and 9352 are the main ones with the remote addresses being the network segments of your Azure Datacenter.

The problem: “Oh it’s a chain validation thing, I’ll just go and turn off Certificate checking…” let me see the options.
(this is what we thought 2+ weeks ago)

Here I have a BizTalk shot of the transportClientEndpointBehaviour with Authentication node set to NoCheck and None (you would set these from code or a config file outside of biztalk)

We found that these currently have NO BEARING whatsoever…2 weeks we’ll never get back.

Don’t be drawn into here, it’s a long windy path and you’ll most likely end up short.

I am currently waiting to hear back from the folks on the product team to see what the answer is on this – BUT for now as a workaround we sat down with a network sniffer to see the characteristics.

Work around:

1. Add some Host Entries

2. Create a dummy site so the checker is fooled into grabbing local CRLs.

Add these Entries to your HOSTs file.

127.0.0.1    www.public-trust.com
127.0.0.1    mscrl.microsoft.com
127.0.0.1    crl.microsoft.com
127.0.0.1    corppki

Download and extract these directories to your DEFAULT WEB SITE (i.e. the one that answers to http://127.0.0.1/…..)
This is usually under C:\inetpub\wwwroot (even if you have sharepoint installed)

-------------------- The nasty error -------------------

The Messaging Engine failed to add a receive location "<receive location>" with URL "sb://<rec url>" to the adapter "WCF-Custom". Reason: "System.ServiceModel.Security.SecurityNegotiationException: The X.509 certificate CN=servicebus.windows.net chain building failed. The certificate that was used has a trust chain that cannot be verified. Replace the certificate or change the certificateValidationMode. The revocation function was unable to check revocation because the revocation server was offline.
---> System.IdentityModel.Tokens.SecurityTokenValidationException: The X.509 certificate CN=servicebus.windows.net chain building failed. The certificate that was used has a trust chain that cannot be verified. Replace the certificate or change the certificateValidationMode. The revocation function was unable to check revocation because the revocation server was offline.

   at Microsoft.ServiceBus.Channels.Security.RetriableCertificateValidator.Validate(X509Certificate2 certificate)
   at System.IdentityModel.Selectors.X509SecurityTokenAuthenticator.ValidateTokenCore(SecurityToken token)
   at System.IdentityModel.Selectors.SecurityTokenAuthenticator.ValidateToken(SecurityToken token)
   at System.ServiceModel.Channels.SslStreamSecurityUpgradeInitiator.ValidateRemoteCertificate(Object sender, X509Certificate certificate, X509Chain chain, SslPolicyErrors sslPolicyErrors)
   at System.Net.Security.SecureChannel.VerifyRemoteCertificate(RemoteCertValidationCallback remoteCertValidationCallback)
   at System.Net.Security.SslState.CompleteHandshake()
   at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
   at System.ServiceModel.Channels.SslStreamSecurityUpgradeInitiator.OnInitiateUpgrade(Stream stream, SecurityMessageProperty& remoteSecurity)
   --- End of inner exception stack trace ---
   at System.ServiceModel.Channels.SslStreamSecurityUpgradeInitiator.OnInitiateUpgrade(Stream stream, SecurityMessageProperty& remoteSecurity)
   at System.ServiceModel.Channels.StreamSecurityUpgradeInitiatorBase.InitiateUpgrade(Stream stream)
   at System.ServiceModel.Channels.ConnectionUpgradeHelper.InitiateUpgrade(StreamUpgradeInitiator upgradeInitiator, IConnection& connection, ClientFramingDecoder decoder, IDefaultCommunicationTimeouts defaultTimeouts, TimeoutHelper& timeoutHelper)
   at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.SendPreamble(IConnection connection, ArraySegment`1 preamble, TimeoutHelper& timeoutHelper)
   at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.DuplexConnectionPoolHelper.AcceptPooledConnection(IConnection connection, TimeoutHelper& timeoutHelper)
   at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
   at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at Microsoft.ServiceBus.RelayedOnewayTcpClient.RelayedOnewayChannel.Open(TimeSpan timeout)
   at Microsoft.ServiceBus.RelayedOnewayTcpClient.GetChannel(Uri via, TimeSpan timeout)
   at Microsoft.ServiceBus.RelayedOnewayTcpClient.ConnectRequestReplyContext.Send(Message message, TimeSpan timeout, IDuplexChannel& channel)
   at Microsoft.ServiceBus.RelayedOnewayTcpListener.RelayedOnewayTcpListenerClient.Connect(TimeSpan timeout)
   at Microsoft.ServiceBus.RelayedOnewayTcpClient.EnsureConnected(TimeSpan timeout)
   at Microsoft.ServiceBus.Channels.CommunicationObject.Open(TimeSpan timeout)
   at Microsoft.ServiceBus.Channels.RefcountedCommunicationObject.Open(TimeSpan timeout)
   at Microsoft.ServiceBus.RelayedOnewayChannelListener.OnOpen(TimeSpan timeout)
   at Microsoft.ServiceBus.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Dispatcher.ChannelDispatcher.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.ServiceHostBase.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at Microsoft.ServiceBus.SocketConnectionTransportManager.OnOpen(TimeSpan timeout)
   at Microsoft.ServiceBus.Channels.TransportManager.Open(TimeSpan timeout, TransportChannelListener channelListener)
   at Microsoft.ServiceBus.Channels.TransportManagerContainer.Open(TimeSpan timeout, SelectTransportManagersCallback selectTransportManagerCallback)
   at Microsoft.ServiceBus.SocketConnectionChannelListener`2.OnOpen(TimeSpan timeout)
   at Microsoft.ServiceBus.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Dispatcher.ChannelDispatcher.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.ServiceHostBase.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfReceiveEndpoint.Enable()
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfReceiveEndpoint..ctor(BizTalkEndpointContext endpointContext, IBTTransportProxy transportProxy, ControlledTermination control)
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfReceiver`2.AddReceiveEndpoint(String url, IPropertyBag adapterConfig, IPropertyBag bizTalkConfig)".

Microsoft AppFabric 1.1 for Windows Server–released!

Mick Badran — Wed, 25 Jan 2012 23:14:06 GMT

Recently there’s been an update to the ‘on-premise’ AppFabric for Windows Server.

Grab the update here - http://www.microsoft.com/download/en/details.aspx?id=27115 (runs on win7, 2008, 2008R2)

What’s new

I’m in the process of updating my components, but the majority of updates seems to be around caching and performance.

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

Read-Through/Write-Behind	This allows a backend provider to be used on the cache servers to assist with retrieving and storing data to a backend, such as a database. Read-through enables the cache to "read-through" to a backend in the context of a Get request. Write-behind enables updates to cached data to be saved asynchronously to the backend. For more information, see Creating a Read-Through / Write-Behind Provider (AppFabric 1.1 Caching).
Graceful Shutdown	This is useful for moving data from a single cache hosts to rest of the servers in the cache cluster before shutting down the cache host for maintenance. This helps to prevent unexpected loss of cached data in a running cache cluster. This can be accomplished with the Graceful parameter of the Stop-CacheHost Windows PowerShell command.
Domain Accounts	In addition to running the AppFabric Caching Service with the NETWORK SERVICE account, you can now run the service as a domain account. For more information, see Change the Caching Service Account (AppFabric 1.1 Caching).
New ASP.NET Session State and Output Caching Provider	New ASP.NET session state and output caching providers are available. The new session state provider has support for the lazy-loading of individual session state items using AppFabric Caching as a backing store. This makes sites that have a mix of small and large session state data more efficient, because pages that don't need large session state items won't incur the cost of sending this data over the network. For more information, see Using the ASP.NET 4 Caching Providers for AppFabric 1.1.
Compression	You can now enable compression for cache clients. For more information, see Application Configuration Settings (AppFabric 1.1 Caching).
Multiple Cache Client Application Configuration Sections	A new `dataCacheClients` section is available that allows you to specify multiple named `dataCacheClient` sections in an application configuration file. You can then programmatically specify which group of cache client settings to use at runtime. For more information, see Application Configuration Settings (AppFabric 1.1 Caching).

Position: Technical BizTalk Developer

Mick Badran — Wed, 11 Jan 2012 12:32:16 GMT

Hi folks, we’ve set a cracking pace into 2012 and are in need of an additional team member.

If you love technology, we love technology and I’d love to hear from you to be part of my team.

You will be stimulated, constantly thinking and challenged – azure, integration, biztlak, sql, windows phone 7 and many other technology areas you’ll be exposed to. Integration is all about the glue we use to achieve the result.

If you’re keen for a chat check out the blurb - http://www.breeze.net/about/jobs.aspx

Cheers,

Mick.

I’m presenting this month at the Windows Azure Sydney User Group (WASUG)

Mick Badran — Mon, 09 Jan 2012 04:18:16 GMT

Thought I’d start off the year with a bang around Azure and what’s been happening in the land of Integration.

So I contacted a Conor Brady to see what was cooking.

The user group is meeting next Thursday 19th Jan 2012.

Here’s the blurb…..

-----------------------------------------

'Integration using Windows Azure Application Integration Services'

Local Integration & Training guru Mick Badran CTO at Breeze Training & Consulting and veteran BizTalk Server MVP will present on 'Integration using Windows Azure Application Integration Services'

The presentation will show how to use Microsoft Windows Azure to be the cornerstone of your integration strategy, whether it’s a small piece or larger deployment. Find out what new tools you can use to extend your existing toolbox and the best way to use them.

This session will cover:

- Strategies on complementing your on-premise <-> cloud integration and what tool to use when.

- High availability solutions with a demo of fault tolerance.

- Casting an eye what’s around the corner to new features coming out of Azure Labs such as EAI, EAI Bridges, EDI – azure style and new XML over HTTP endpoints.

------------------------------------------

Here’s the link to REGISTER - http://www.eventbrite.com/event/2739308345

See you there!

Mick.

Teched 2011 – Gold Coast: How “the Cloud” can help you integrate

Mick Badran — Thu, 11 Aug 2011 03:06:03 GMT

What a place…the Gold Coast!!!

Any chance to get back there… and this year is looking to be a fantastic 2 day pre-conference training together.

In the training there’ll be no MS speak!! I promise “We’re all in…” …(washing mouth out with soap).

First things first – everyone you speak to will pronounce ‘Azure’ differently (I once had 3 martial arts instructors all speak their own flavour of ‘Korean’ to me).
You’ll get:
1) ‘Aaaaaazzzzre’
2) ‘Azzzz-cloud’

Now here in Australia we’re standardising (our English-Australian) to Azurey!

Azurey is our official term, which fits alongside ‘Timmy’, ‘Barbie’ and ‘Daveo’… but not Shazza.

What I want to explore with you are all the different options and components that you could utilise. Having been through several cloud based solutions and building a cloud based solution over the last 2 years.

So we can use a combination of the available technologies to alleviate some of the in-house problems (e.g. firewall settings, h/w order and provisioning, server space) while still maintaining *very* good ownership over it.

One thing is clear right now – with this new landscape the focus has returned to the Developer to be mindful of what resources they use and HOW they use them.

The price of your solution starts right now from the ground up with the Developer!
(Previously we’ve had limitless memory, disk, cpu, connections, sockets, select * from customers… – developers rarely care)

So the cost model – What do you get charged for?
(short answer – nearly everything)

If you can design a solution with:
1) no use for SQL Azure –as it currently costs a bomb to host a DB.
You could use – SQLCE locally or Azure Storage (Table, Queue, blob) which is cheap as chips.

2) limit your Service Bus Connections – both client and server count as a connection. The connections are averaged out over a day/month and are sampled every 5 mins, but you certainly don’t want to rack up 100s of connections. A cheaper alternative is to expose a WCF Endpoint (via a worker role) and have a process communicate with the Servicebus endpoint handling the requests. This counts for 2 connections (1 client, 1 server) and is well within the 5 pack.

3) Only data out is charged – not in.

4) Compute VM sizes limit bandwith – across all your compute VMs e.g. small, there is bandwidth limitations that is enforced whether you have 1 or 10 VMs. Be mindful of that.

5) We can ‘monitor’ our cloud machines and even get back perf counters on each – just to give you that feel good feeling.

Well anyway I must go tweak some F# (best thing I’ve seen in a long while…another story)

Here’s the official story @ TechEd – hope to see you there folks!

http://australia.msteched.com/preconferencetraining

Official Blurb!

How “the Cloud” can help you integrate – Microsoft for Developers

With the excitement of technology moving towards “the Cloud” come and learn exactly what this means to your business and how your development projects can leverage the Windows Azure Platform without re-architecting your environment. Should you invest in private cloud, move your application to the public cloud, choose a hybrid approach or keep the application on-premise?

This two-day development workshop led by renowned Integration Experts provides delegates with an early opportunity to gain insight and hands-on experience with the Windows Azure Platform including Windows Azure AppFabric, SQL Azure, Windows Server AppFabric and BizTalk AppFabric Connect.

This developer workshop focuses on maximising your existing integration technology investment for an on-premise solution, including architectural design considerations, real world tips and techniques and hands-on experience with using the integration tools available today.

Delivered through workshop style presentations and hands-on lab exercises, this technology focused pre conference training will assist with designing and developing your company roadmap to the Cloud.

Azure Service Bus: Required Firewall Rules - 'watchdog....'

Mick Badran — Wed, 22 Jun 2011 02:24:38 GMT

So you've got an on-premise WCF Service and you're going to expose the endpoint to the Cloud via ServiceBus.

I'm with a client excited about the prospect of Azure and using ServiceBus for connectivity for our local WCF Services.

Remember ServiceBus is touted as the firewall friend communications mechanism.

Should be pretty easy right? - just follow an article like - http://msdn.microsoft.com/en-us/library/ee732535.aspx

If you are on a Secure Server - i.e. one that doesn't have default open slather access to the internet by default you will fall well short.
(nb: the Azure ServiceBus documentation is a little thin here also. ie no mention whatsoever)

You will get 'can't contact watchdog.servicebus.windows.net' and many others....So....

After much head banging Scotty sat down one rainy day and looked at the full conversation to establish a connection to the cloud via Service Bus

NB: XXXX is your ServiceBus endpoint name you configured in the Azure Management Portal earlier. This endpoint lives in the Azure Singapore Data Center

When ConnectionMode = TCP (Hybrid)

1. CNAME lookup for watchdog.servicebus.windows.net > returns ns-sb-prod-sn1-001.cloudapp.net

2. Connect to ns-sb-prod-sn1-001.cloudapp.net (port 9350)

3. CNAME lookup for XXXX-sb.accesscontrol.windows.net returns ns-ac-prod-sin-001.cloudapp.net

4. Connect to ns-ac-prod-sin-001.cloudapp.net (port 443)

5. CNAME lookup for XXXX.servicebus.windows.net returns ns-sb-prod-sin-001.cloudapp.net

6. Connect to ns-sb-prod-sin-001.cloudapp.net (port 9351)

When ConnectionMode = Http

1. CNAME lookup for XXXX-sb.accesscontrol.windows.net returns ns-ac-prod-sin-001.cloudapp.net

2. Connect to ns-ac-prod-sin-001.cloudapp.net (port 443)

3. CNAME lookup for XXXX.servicebus.windows.net returns ns-sb-prod-sin-001.cloudapp.net

4. Connect to ns-sb-prod-sin-001.cloudapp.net (port 80)

Also, when we lock this down to https endpoint step 4 above will be over 443

So the complete firewall rules to support both modes should be:

· watchdog.servicebus.windows.net (9350-9353)

· ns-sb-prod-sn1-001.cloudapp.net (9350-9353)

· XXXX-sb.accesscontrol.windows.net (443)

· ns-ac-prod-sin-001.cloudapp.net (443)

· XXXX.servicebus.windows.net (80, 443, 9350-9353)

· ns-sb-prod-sin-001.cloudapp.net (80, 443, 9350-9353)

Note the difference between ns-sb-prod-sn1-001.cloudapp.net and the others ns-ac-prod-sin-001.cloudapp.net, ns-sb-prod-sin-001.cloudapp.net

Hopefully you won't get caught out at a client site asking for firewall changes, one at a time as you discover them.

Enjoy,

Mick + big thanks Scotty for the details.

BizTalk 2010: Talking the REST language

Mick Badran — Thu, 17 Mar 2011 03:21:25 GMT

As you may/may not know native Restful support is a little lacking in BizTalk 2010.

A ‘little’ massaging is needed.

By plugging in a couple of classes into the WCF stack, BizTalk sits in the middle quite nicely.

Netin Mehrotra from MS has come to the rescue – he provides a great walk through article and sample code to boot.

Here’s the REST SAMPLE CODE

Here’s the REST ARTICLE

Enjoy guys.

The alternative is to create your own WCF Service in Windows Server AppFabric hosted in IIS and then you’ve still got the problem of ‘how’ to talk to BizTalk.

Choices…choices… :)

Recent Launch of AppFabric CAT blog...

Mick Badran — Mon, 30 Aug 2010 03:50:58 GMT

Hi folks, an email floated across my desk from Tim Wieman today tell me about a new AppFabric CAT blog.

Thanks Tim.
--- snippet ---

Recently as part of building the Windows Server AppFabric Customer Advisory Team (or AppFabric CAT for short). This team brings under one “virtual roof” others like me from the team formerly known as the “BizTalk Rangers”, plus other technology experts in Windows Server AppFabric, AppFabric Caching, WF, WCF, StreamInsight, EF, etc.

The new team blog is our commitment to deliver technical guidance and share best practices with the rest of the world-wide community. We are also working on the AppFabric CAT portal, a brand-new web site that will serve the purpose of the “one-stop shop” for all the great deliverables that our team will be producing for the community going forward (similar to sqlcat.com).

Please check out our team blog at http://blogs.msdn.com/appfabriccat.

TechEd 2010: Mastering Microsoft Integration Solutions

Mick Badran — Fri, 27 Aug 2010 04:40:00 GMT

Well as TechEd 2010 draws to a close this year in Australia, I had a great time getting away from it all and certainly experiencing a couple of firsts. For me this was one of the better TechEd’s I had been to – the sessions were a little light on, but the labs + exams made up for that big time.

So Scotty and I developed an Integration Pre Conference Training Session aimed at working out which MS Integration technology to run where – unscrambling the mess. We got a great turn out for the training in terms of numbers – we beat SharePoint 2010 dev + admin!!! :)

For all of you whom I had the pleasure of training this week – well done! I hope you enjoyed it and it was great sharing that time with you. The sun, sand, BizTalk and Azure…what could be better?? :)

As promised – here are the slides from those two days.

Keep smiling,
Mick.

Microsoft Integration Story… When to use what Technologies Where

Mick Badran — Tue, 20 Jul 2010 16:46:36 GMT

Hey folks,

As we’re all aware there’s more than one road that leads to Rome when dealing with integration. When to use SSIS? For what? What about MSMQ? AppFabric and BizTalk etc.

At TechEd this year I’ve decided to run some preconference training dealing with this exact issue across many different Microsoft Integration Technologies.
(This is one of the biggest questions I get from customers)

If you’re heading to the Gold Coast this year, then this training is before TechEd – get up a couple of days early and then be fully charged and armed with all your questions….

---- here’s the official blurb----

When to use what Technologies Where [LINK is Here]

AppFabric, Azure Storage, BizTalk 2010, BizTalk Adapter Pack, WCF, WF, Oslo, MSMQ, .NET4 Distributed Caching, SQL Service Broker, SSIS and SharePoint 2010 Service Applications...to name a few technologies to be confused about.

There is no silver bullet for application integration. Different situations call for different solutions, each targeting a particular kind of problem. While a one-size-fits-all solution would be nice, the inherent diversity of integration challenges makes such a simplistic approach impossible. To address this broad set of problems, Microsoft has created several different integration technologies, each targeting a particular group of scenarios.

Together, these technologies provide a comprehensive, unified, and complete integration solution.

Come on a 2-day adventure examining each of these technologies and reviewing the When, Why's and How's on each, with their own distinct role to play with integrating applications. When you come through the other side you'll be able to slot each of these technologies into a *practical* use.

This developer workshop is based on real world examples, real world problems and real world solutions.

Join me and be prepared to roll up your sleeves and unravel the maze that awaits....

TECHED LINK

Dublin finally gets a name "Windows Server AppFabric"

Mick Badran — Thu, 19 Nov 2009 22:12:32 GMT

We're moving into a public beta of ~~Dublin~~ "Windows Server AppFabric" which you can grab from HERE.

What does it mean - here's a blurb from the site.

So Velocity (distributed caching mechanism) is rolled up into this Beta (previously a MS Partner did some benchmarking on Velocity which you can find a great white paper HERE)

Previously myself and Scotty wrote a hefty technical Dublin Course which the folks at TechEd loved - we did this on some early bits of 'Dublin'. Realtime monitoring + tracking as well as recoverability were some highlights of our 3D Realtime maze process we built up in the labs.

Here's a blurb from the AppFabric server (it's a shame that SP2010 didn't use this framework for it's WF hosting...but that would have impacted delivery)

Enjoy

-------- Snippet ----------

Windows Server AppFabric has these core capabilities:

For Web applications, AppFabric provides caching capabilities to provide high-speed access, scale, and high availability to application data. This feature was previously codenamed "Velocity"
For composite applications, AppFabric makes it easier to build and manage services built using Windows Workflow Foundation and Windows Communication Foundation. This feature was previously codenamed "Dublin."