This post is in continuation to the blog post yesterday announcing a sample on how to do a SQL Azure lookup using Service Bus EAI Bridges.
- The post is available here: http://blogs.msdn.com/b/nitinme/archive/2012/05/25/sample-using-service-bus-eai-bridges-for-sql-azure-lookup.aspx
- The sample is available here: http://code.msdn.microsoft.com/Using-EAI-Bridges-with-SQL-be2b5761
In this post, I present to you an end-to-end tutorial (as detailed as it could get) on how to create your own Service Bus EAI application to perform a SQL Azure Lookup. In other words, lets just say, that I wrote the sample I mentioned earlier using the set of steps that I have documented in this tutorial:
Here’s a link to the tutorial: http://msdn.microsoft.com/en-us/library/windowsazure/jj136830.aspx
This tutorial is based around a business scenario involving two organizations in the Healthcare industry. Northwind Traders is a healthcare service provider that handles medical insurance claims for an insurance provider, Humongous Insurance. Northwind sends insurance claims as flat file messages to Humongous Insurance. Humongous Insurance processes these claims and stores them in an in-house using an on-premise SQL Server database. Humongous Insurance wants to deploy this business process as an application on Windows Azure. Humongous Insurance decides to use the integration capabilities in the April 2012 release of Windows Azure Service Bus EAI and EDI Labs to deploy this application on the cloud.
Apart from demonstrating the SQL Azure lookup capability of the EAI bridges, the tutorial also describes how to use the following features of the EAI bridge:
- Processing flat file messages by using XML One-Way Bridge. For more information, see Flat-file Support In One-Way Bridge.
- Creating a flat-file schema by using the Flat File Schema wizard. For more information, see How to Use the Flat File Schema Wizard.
- Using an FTP source to send messages to an XML One-Way Bridge. For more information, see Using FTP Source.
- Tracking a message as it gets processed through the bridges. For more information, see Operational Tracking of Messages Processed by the Bridge
I encourage you to go ahead and run the tutorial to build your own application. If you just want to see how this feature works without going into the concepts and the details, you have the sample here.