Book Image

Microsoft Windows Server AppFabric Cookbook

Book Image

Microsoft Windows Server AppFabric Cookbook

Overview of this book

Windows Server AppFabric provides a set of integrated capabilities that extend IIS and the Windows Server platform making it easier to build, scale and manage composite applications today. Windows Server AppFabric delivers the first wave of innovation within an exciting new middleware paradigm which brings performance, scalability and enhanced management capabilities to the platform for applications built on the .NET Framework using Windows Communication Foundation and Windows Workflow Foundation.'Microsoft Windows Server AppFabric Cookbook' shows you how to get the most from WCF and WF services using Windows Server AppFabric leveraging the capabilities for building composite solutions on the .NET platform. Packed with over 60 task-based and immediately reusable recipes, 'Microsoft Windows Server AppFabric Cookbook' starts by showing you how to set up your development environment to start using Windows Server AppFabric quickly. The book then moves on to provide comprehensive coverage of the most important capabilities provided by Windows Server AppFabric, diving right in to hands-on topics such as deploying WCF and WF applications to Windows Server AppFabric and leveraging the distributed caching, scalable hosting, persistence, monitoring and management capabilities that Windows Server AppFabric has to offer, with recipes covering a full spectrum of complexity from simple to intermediate and advanced.

Related Content you might be interested in

Current Title:

Small book image
Microsoft Windows Server AppFabric Cookbook
Jul, 2012 | 428 pages
No titles found
Table of Contents (16 chapters)
Microsoft Windows Server AppFabric Cookbook
Microsoft Windows Server AppFabric Cookbook
Credits
Credits
Foreword
Foreword
About the Authors
About the Authors
About the Reviewers
About the Reviewers
www.PacktPub.com
www.PacktPub.com
Preface
Preface
Free Chapter
1
Installing Windows Server AppFabric
Installing Windows Server AppFabric
Introduction
Installing Windows Server AppFabric
Configuring Windows Server AppFabric (hosting and monitoring)
Configuring Windows Server AppFabric (caching)
Installing Cache Client Assemblies
Changing the Windows Server AppFabric configuration after installation
Starting a Caching service
Troubleshooting Windows Server AppFabric — configuration errors
Troubleshooting Windows Server AppFabric — auto restart issues
2
Getting Started with AppFabric Caching
Getting Started with AppFabric Caching
Introduction
Initializing Cache Client using code
Initializing Cache Client using configuration
Programming AppFabric Cache Client
Using AppFabric Cache via the ASP.NET provider model
Using AppFabric local cache
Using the AppFabric cache management tool
Building a custom provider model
Handling common Windows Server AppFabric caching errors
3
Windows Server AppFabric Caching — Advanced Use Cases
Windows Server AppFabric Caching — Advanced Use Cases
Introduction
Using regions in cache
Using tags in cache
Using optimistic concurrency
Using pessimistic concurrency
Setting up expiration
Setting up eviction
Setting up notifications
Using performance counters
Troubleshooting throttling
Troubleshooting eviction
Setting up read through — write behind
4
Windows Server AppFabric Hosting Fundamentals
Windows Server AppFabric Hosting Fundamentals
Introduction
Installing the Web Deployment tool (Web Deploy)
Packaging services for deployment with Web Deploy
Hosting WCF services
Hosting WCF REST services
Hosting basic workflow services
5
More Windows Server AppFabric Hosting Features
More Windows Server AppFabric Hosting Features
Introduction
Hosting long-running workflow services
Taking advantage of WAS and Auto-Start
Hosting Windows Azure Relay services
Using common Server AppFabric hosting commandlets
6
Utilizing AppFabric Persistence
Utilizing AppFabric Persistence
Introduction
Using Windows Server AppFabric workflow persistence
Programmatically querying persisted workflow instances
Programmatically controlling persisted workflow instances
Developing an Instance Store provider
Developing an Instance Query provider
Developing an Instance Control provider
Registering and configuring custom store, query, and control providers
7
Monitoring Windows Server AppFabric Deployment
Monitoring Windows Server AppFabric Deployment
Introduction
Collecting events from WCF and WF services
Viewing and classifying events in the AppFabric Dashboard
Enabling tracing and evaluating trace logs with WCF
Creating a customized tracking profile for WF services
Accessing the Monitoring DB
Building a custom dashboard
Using monitoring database cmdlets
Monitoring cache cluster health
8
Scaling AppFabric Hosting, Monitoring, and Persistence
Scaling AppFabric Hosting, Monitoring, and Persistence
Introduction
Creating an initial base configuration
Adding and removing servers from the farm
Application deployment on the farm
Configuration and management on the farm
Automating deployment with scripts
9
Configuring Windows Server AppFabric Security
Configuring Windows Server AppFabric Security
Introduction
Running caching services using Domain accounts
Setting up security for persistence stores
Securing Windows Server AppFabric's monitoring store
Securing the Event Collection service

Introduction

Windows Server AppFabric builds on top of .NET Framework's Windows Communication Foundation and Windows Workflow Foundation (WF) and simplifies the scenario of hosting, managing, and monitoring long-running and durable workflows. Windows Server AppFabric's persistence enables two key use cases, which we'll look at now.

Durable application scale out

Windows Server AppFabric is a middleware platform and for most of the deployments, it will run on a distributed server farm. Windows Server AppFabric's Hosting subsystem uses its persistence capabilities to allow WF-based workflows to become scalable and durable. Windows Server AppFabric's provides its default SQL Server based persistence provider (also known as Instance Store), which allows these workflows to become durable.

Computational resources

Instead of keeping long running workflows sitting idle in memory (while they wait for human interaction or an external system impetus) and letting them consume memory/computational resources...

Previous Section
End of Section 2
Next Section