1. BizTalk Azure The more things change the more they stay the same Bon Jovi Jon Fancey Affinus

2. Overview  What is “BizTalk Azure”?  Why is “BizTalk Azure” in quotes?  Will this rock my world?  Let’s have a look at it then  When and what  What’s the roadmap

3. Who am I?  Founder of Affinus  Specialists in hardcore development on the Microsoft platform  BizTalk, Azure, SharePoint, WPF, WCF mainly  BizTalk MVP  6 years in a row  Speaker, writer, etc  MSDN, TechEd, DevWeek…  Pluralsight instructor

4. Assumptions  You are developers  You understand BizTalk  You’ve not really spent much time with Azure Integration Svcs

5. What is it?  A way to connect cloud (internet) accessible resources  And integrate with other cloud resources (partners)  Or your own on-premises systems  Or with Windows Azure resources  EAI and EDI – more later  A hosting platform  No hardware to provision  In fact very high level of abstraction  A management platform  Portal to setup, manage and view integration solutions

6. The Basics  Azure Integration Services EAI and EDI CTP  April 2012 most recent release  AKA “BizTalk Azure”*  Based on Azure fabric and capabilities  Service Bus  Queues, topics  SQL Azure  Portal FTP Server Azure Integration Services BridgeQ *see previous caveat

7. Your place Relays  Mechanism to connect and store/forward messages  First building block of Azure Integration  Service bus  Register end point and wait for messages to be delivered  Publically visible  Secured using ACS FTP Server Azure Integration Services Bridge EP Service Bus My app

8. Take it to the Bridge  Bridges provide the conduit over which stuff happens  It’s all messages over service bus  A bridge is a pipeline (that’s actually a workflow)  The pipeline has stages with pre-configured components  One way and request/response Azure Integration Services Bridge Validate Service Bus Enrich Transform Enrich Route

9. Demo : basic connectivity

10. Transformation  New mapper  CTP release not based on XSLT  Provides enhancements to simplify common tasks  Looping  Expressions  Maps can be configured, deployed and reused across solutions

11. On-premises Connectivity  Comes with BizTalk LOB adapters  SQL, SAP, Oracle etc.  Service Bus Connect  Provides a relay endpoint for Azure to pipe messages to  Relay opens connection and Azure holds it open  Responses are actually request messages  When response received, a new call is made to SB to maintain it  Avoids firewall issues, port 80 outbound  Can elevate to P2P if configured  Virtual Networks  In preview, could provide alternative to SB Connect  AD Integration  VPN etc

12. Demo : on prem

13. Web Access  For the CTP the labs environment is used  portal.appfabriclabs.com  edi.appfabriclabs.com  For production the standard Azure portal will be used  Web portal in CTP geared towards EDI  Trading partner management  Agreements  Tracking

14. Demo : portal

15. Primary Interfaces  Visual Studio  2010 currently  Win7 (but can run on Win8)  Portal  Main Azure Portal  EDI portal  REST API  Leveraged by VS, full fidelity with UI tools  Provides more capabilities than tools currently expose  Management, e.g. deployment  Monitoring, e.g. tracking

16. Tracking  How to Track  EAI and EDI flows  Even though portal doesn’t surface EAI tracking  Can access via REST interface  Track points  Flow data  Message properties  Can also archive (save) messages (via portal)

17. Comparison with BizTalk BizTalk“BizTalk Azure” Map (aka transform) Schema PipelineBridge AdapterBridge endpoint (src/dest) Orchestration? BindingBridge configuration Subscription~Route, Topic Admin ConsoleEDI portal TPMTPM in EDI portal BTSTaskPowershell BAM? Tracking BRE?

18. CTP Limitations  It’s a CTP…  Expect improvements before release  Passthru scenarios  FTP endpoint assumes flat file  If you want to XML you need Passthru  Manual edit via REST  Start and stop endpoints  Hard to keep track of what bridges are deployed  You don’t want to be burning bridges but…  Can get in a state where you need to just delete them via REST API

19. Call to action  BizTalk Azure is coming  Key message is ONE BizTalk  On prem, in cloud (PaaS and Iaas), hybrid  BizTalk Azure is a new way to create integration solutions  In the cloud, quick startup  New capabilities  Portal  enhancements to batching, mapping + more  Use what you know with BizTalk  To leverage this new platform  Schemas, maps, pipelines  Find out more  http://msdn.microsoft.com/en-us/library/windowsazure/hh689864.aspx http://msdn.microsoft.com/en-us/library/windowsazure/hh689864.aspx

20. Contact Me  Jon.Fancey@affinus.com Jon.Fancey@affinus.com  @JonFancey  WARNING - Not all technical goodness  http://www.jonfancey.com http://www.jonfancey.com  And of course, www.affinus.com