a507ed33-cec0-4789-bd56-32a8b7a494ba (5 left)

Microsoft used to provide Enterprise Application Integration (EAI) and Electronic Data Interchange (EDI) capabilities through BizTalk. With the release of Windows Azure Service Bus EAI and EDI labs CTP, it envisions to provide same capabilities as Platform-as-a-Service (PaaS). It now unlocks the power of middleware in the cloud!

What is included in this CTP?

1. Enterprise Application Integration
   • Service Bus Connect : This feature allows an application in the cloud to communicate to Line-of –Business(LOB) system residing on-premises using LOB BizTalk Adapter Pack.For this release it supports, SQL Server, Oracle Database, Oracle E-Business Suite, SAP and Siebel eBusiness Applications.
   • Transformations: This allows transforming a message from one schema to another schema. This is a feature similar to BizTalk Map with a new face lift. Now the functoids are called Operations in Maps.
   • Bridges: Enable Service mediation patterns such as VETR (Validate, Extract\Enrich, Transform and Route)
2. Electronic Data Interchange: With Trading Partner Management Solution on the cloud, It is possible to configure to send and receive messages from Business Partners using the portal here.

To get started, download the SDK samples from http://go.microsoft.com/fwlink/?LinkID=184288 and the tutorial & documentation from http://go.microsoft.com/fwlink/?LinkID=235197

Two clients are developed to send and receive messages to\from AppFabric Service Bus.

Currently, these clients are developed on Windows Azure AppFabric SDK v1.5 September Release and available for download at http://appfabricservicebus.codeplex.com/
Walkthrough to use Test Clients

Send Client

Connect to AppFabric by clicking on menu File>>Connect. This action opens a Connection Explorer.

Choose Service Namespace from dropdown if the settings exist in NamespaceConfiguration.xml located in application folder. If not, enter credentials to connect to Windows Azure AppFabric.

Choose Communication Object and list to connect

Enter a message in Message tab and set message properties in Properties tab. Click on Send button to send a message.

Receive Client

Choose a Communication Object and Queue\Topic and Subscription list from dropdown.

Click on Poll Button to receive messages.

Click on Message Id in Received Messages to view message and its properties.

Update[01/17/2012]: MSDN now has a comprehensive  list. Click Here

Note: Comparison list is slightly outdated with the new release of Windows Azure SDK 1.5 and as the products evolve.

1. Make sure Windows Azure AppFabric SDK is Installed.

2. Make sure below settings exist in machine.config file if not add manually

<behaviorExtensions>

…..

<add
name=“connectionStatusBehavior“
type=“Microsoft.ServiceBus.Configuration.ConnectionStatusElement, Microsoft.ServiceBus, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35“ />

<add
name=“transportClientEndpointBehavior“
type=“Microsoft.ServiceBus.Configuration.TransportClientEndpointBehaviorElement, Microsoft.ServiceBus, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35“ />

<add
name=“serviceRegistrySettings“
type=“Microsoft.ServiceBus.Configuration.ServiceRegistrySettingsElement, Microsoft.ServiceBus, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35“ />

</behaviorExtensions>

<bindingElementExtensions>

…..

<add
name=“tcpRelayTransport“
type=“Microsoft.ServiceBus.Configuration.TcpRelayTransportElement, Microsoft.ServiceBus, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35“ />

<add
name=“httpRelayTransport“
type=“Microsoft.ServiceBus.Configuration.HttpRelayTransportElement, Microsoft.ServiceBus, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35“ />

<add
name=“httpsRelayTransport“
type=“Microsoft.ServiceBus.Configuration.HttpsRelayTransportElement, Microsoft.ServiceBus, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35“ />

<add
name=“onewayRelayTransport“
type=“Microsoft.ServiceBus.Configuration.RelayedOnewayTransportElement, Microsoft.ServiceBus, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35“ />

</bindingElementExtensions>

<bindingExtensions>

…..

<add
name=“basicHttpRelayBinding“
type=“Microsoft.ServiceBus.Configuration.BasicHttpRelayBindingCollectionElement, Microsoft.ServiceBus, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35“ />

<add
name=“webHttpRelayBinding“
type=“Microsoft.ServiceBus.Configuration.WebHttpRelayBindingCollectionElement, Microsoft.ServiceBus, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35“ />

<add
name=“ws2007HttpRelayBinding“
type=“Microsoft.ServiceBus.Configuration.WS2007HttpRelayBindingCollectionElement, Microsoft.ServiceBus, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35“ />

<add
name=“netTcpRelayBinding“
type=“Microsoft.ServiceBus.Configuration.NetTcpRelayBindingCollectionElement, Microsoft.ServiceBus, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35“ />

<add
name=“netOnewayRelayBinding“
type=“Microsoft.ServiceBus.Configuration.NetOnewayRelayBindingCollectionElement, Microsoft.ServiceBus, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35“ />

<add
name=“netEventRelayBinding“
type=“Microsoft.ServiceBus.Configuration.NetEventRelayBindingCollectionElement, Microsoft.ServiceBus, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35“ />

</bindingExtensions>

1. Hosting Services

2. Caching Services

• Click Next

• Check Set monitoring configuration

• Choose Monitoring provider and Click on Configure

• Check Register AppFabric monitoring store in root web config and Initialize monitoring store

• Choose Database from the list or enter the database name to be created and click on OK

• Click on Yes in Confirmation dialog

• Monitoring store registered!

• Check Set Persistence configuration

• Choose Persistence provider and click on Configure

• Check Register AppFabric persistence store in root web config and Initialize persistence store
• 
• Choose Database from the list or enter the database name to be created and click on OK

• Click on Yes in confirmation dialog

• Persistence store Initialized!

• Click on Next

• Click on Set Caching Service configuration

When specifying the Caching Service configuration provider, there are two options available:

1. XML – Caching Service configuration information is stored in an XML file on a network file share.
2. SQL Server Distributed Cache Configuration Store Provider – Caching Service configuration information is stored in a SQL Server database.

• Choose XML for Workgroup scenarios
• If your computer is part of a workgroup, you must change the Caching Service account. Use a local account that exists on all computers participating in the cluster and use the same password for the account on all computers. For configuration, the local account must have local administrator privileges, and must not be a built-in account. This step is not necessary for domain-joined machines.
• Choose a valid UNC File share path and click on Next

• Check Firewall exceptions and click on Next

• Click Yes on confirmation dialog

• Click on Finish !

BizTalk Azure Adapters

BizTalk Azure Adapters SDK 1.0 provides the capabilities to BizTalk Server 2009 to Integrate on-premise application with cloud based applications and services running on Windows Azure Platform.

SDK 1.0 is capable to connect on-premise application with Azure Live Framework and .Net Services.

BizTalk Adapter for .Net Services can Send\Receive messages.

BizTalk Adapter for Live Mesh can Receive Notifications and Mesh Objects.

Adapters can be downloaded here.

BizTalk HIPAA 5010 Schema pack hotfix has been released from Microsoft under the TAP program.

Please follow the instruction in read me document before installing the setup.