Hybrid Solution Integration


Published on

A clear picture of building hybrid solution using the Microsoft Integration Stack. Hybrid Solutions: Integration BizTalk Server 2013, Windows Azure Service Bus, BizTalk Services and REST.

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Little introduction of myself
  • Now that term hybrid is clear explain/tell what people can expected from this session; Level 200/300 session
  • Explain the term hybrid
  • Set scope to Microsoft. There are many IaaS, PaaS and SaaS providers. This presentation focusses on Microsoft Integration Stack and what it offers when it comes to hybrid solutions.
  • What are your hybrid scenario’s:Distinction between on premise and cloud, you have B2B enhanced now with BizTalk Services (will not be further discussed in this session), integration with SaaS and other services (e.g. REST). Hybrid Apps:Application integration continues to happen on-premisesHarness cloud for elastic compute and to access external applicationsLeverages the cloud for scale, high availability and disaster recoveryB2BSecurely connect to your trading partnersHarness cloud for extensibility, self-service on-boarding and rich message trackingSupport more than 10,000 schemasSAAS Integration:Connect to a host of SaaS services from your on-prem or SaaS applicationsSupport store-and-forward scenariosIntegrate with external identity providers like Windows Live, OAuth
  • BizTalk Offering with BizTalk 2013. What can you do with this version and what makes it so special.
  • WCF-based new adapters, what are they, considerations
  • Service Bus offering with BizTalk 2013. What can you do with it.
  • Show Portal, demo solution, walktrough the configuration
  • Sample of on-premise – Cloud. Exposing data or process in the cloud. Considerations are availability, security (who can access the data) and data itself (not every data needs to be exposed).
  • Show configuration of the adapter, demo solution, show endpoints and so on.
  • Talk about REST.
  • Consuming a REST Endpoint, challenges are contract, security (latency, depending if it is public or not) and availability (depending on where services is hosted, SLA).Another sample is pushing data to Windows Azure Storage Account. [TODO] Challenges for this
  • Show demo, endpoint Rest Service FAA, configuration of the adapter. Mention security in case you consume an endpoint that requires authentication.
  • BizTalk Services offering
  • Show Portal, demo solution, security using custom code.
  • Recap of the session
  • Call to action, what can the audience do?
  • Point out the labs/discussions day 2
  • Hybrid Solution Integration

    1. 1. Hybrid Solutions: Integration BizTalk Server 2013, Windows Azure Service Bus, BizTalk Services and REST
    2. 2. Steef-Jan Wiggers Architect & Microsoft Integration MVP • Author • Speaker • Community • Runner
    3. 3. Key takeaways  Give a clear picture of building hybrid solution using the Microsoft Integration Stack  Considerations when building hybrid solutions  View on the different integration components 3
    4. 4. What does Hybrid mean? 4
    5. 5. Scope 5
    6. 6. Different flavors of hybrid integration solutions 6
    7. 7. Hybrid solutions Windows Azure SaaS Apps Devices Partners BizTalk Services Service Bus BizTalk Server LOB MAINFRAME ERP DATABASES 7
    8. 8. Hybrid scenario’s HYBRID APPS B2B SAAS INTEGRATION 8
    9. 9. BizTalk Server 2013 • Run BizTalk Server in the cloud (IaaS) • • Virtual Machine in Windows Azure Connectivity with SaaS solutions • Brokered (Service Bus) • Direct (Relay) • Platform as a Service (PaaS) • Deploy integration solutions in Windows Azure 9
    10. 10. VM in the Cloud – IaaS  Benefits – – Procurement –  Lower TCO Elasticity/Availability Connectivity – –  VPN Web Services Provisioning – Manually quick create or – Automated using PowerShell – Upload existing Image (VHD) 10
    11. 11. New (WCF-based) adapters: BizTalk 2013  Relay: WCF-BasicHttpRelay, WCF-NetTcpRelay, WCFWebHttp  Service Bus: SB-Messaging  REST: WCF-WebHttp  SFTP adapter Key innovation feature of this BizTalk version are the cloud based adapters! 11
    12. 12. Service Bus Middleware in the Cloud – Cloud Hosted Features • Relay Services • Queues • Pub/Sub Reliable Messaging • Notifications • Windows Azure Portal 12
    13. 13. SB-Messaging Adapter Benefits:  Reliable messaging  Load levelling/load balancing  Low costs, fast Time-to-market Features: • Brokering (Asynchronous messaging) • Leverages Access Control Service (ACS) for cloud based authentication • Sessions (FIFO) 13
    14. 14. Use case: Register running times Topic Subscriptions BizTalk Server Data Store 14
    15. 15. DEMO SB-Messaging 15
    16. 16. Relay adapters Benefits:  Expose existing interfaces to the cloud quickly and easily  Extend reach of data or processes  Low cost, fast Time-to-market Features: • Initially introduced as a BizTalk 2010 Feature pack (Connect for services) • Expose local and cloud endpoints • Leverages the BizTalk WCF Publishing Wizard • Provides 1 way Asynchronous or 2 way Synchronous Request-Response Interactions • Leverages Access Control Service (ACS) for cloud based authentication 16
    17. 17. Sample scenario with WCF-NetTcpRelay  Extend reach of existing integration solutions to the cloud Custom View Relay Service Behind firewall on premise ERP Custom Process Line of Business Integration 17
    18. 18. DEMO WCF-NetTcpRelay 18
    19. 19. REST Benefits: • Support for ‘Lightweight’ integration scenarios • Many SaaS and Cloud platforms are adopting RESTful APIs (SalesForce, Twitter, Google, Azure) • Mobility Features: • Support for exposing and consuming ‘RESTful’ services • Can be used with and without Service Bus integration • Provides 1 way Asynchronous or 2 way Synchronous Request-Response Interactions • Leverages Access Control Service (ACS) for cloud based authentication 19
    20. 20. Sample scenario consuming REST Endpoint ERP Behind firewall on premise Integration Custom Application Line of Business 20
    21. 21. DEMO WCF-WebHttp 21
    22. 22. Windows Azure BizTalk Services  Dedicated Service • Dedicated service hosted & managed by Microsoft in its subscription • Provides isolation for compute and storage • Predictable • Secure  performance sandboxed environment for each customer/tenant Infrastructure managed by Microsoft, App by user • 99.9% uptime SLA from Microsoft • Service Health monitoring integrated with Azure Portal • BizTalk applications monitoring through BizTalk Portal • Raw tracking and monitoring information available in user store 23
    23. 23. Windows Azure BizTalk Services  EAI Service • • Out of the box support for common integration patterns •  B2B Drag and drop integration solution development Connectivity to on-premises LOB systems out of the box Service • Trading partner management and supplier on-boarding • Support for X12 and AS2 • Enterprise capabilities such as Archiving, Ack correlation and NRR  Extensible Platform • Rich message processing • Customization with code for transforms and pipeline stages • Trading Partner Management API for custom experiences 23
    24. 24. BizTalk Services - Bridge Lob Relay (Service Host) Management Service Server Explorer (Visual Studio) REST API PowerShell CmdLets 24
    25. 25. BizTalk Services - Bridge Basic building block for building your integration platform A Bridge is a single message processing unit with 3 parts: 25
    26. 26. Use case: Runner Data Lob Relay (Service Host) 26
    27. 27. DEMO Windows Azure BizTalk Services 27
    28. 28. Hybrid Solutions – Consideration  Security (access to resources, identity management)  Governance (changing schema’s)  Availability (hosting of your endpoints, SLA’s)  Increased load (more devices, platforms)  REST Orientation (lots of API’s are REST based)  Interoperability (support for different platforms)  Latency (request for tokens)
    29. 29. Wrap up  Different options to choose from when building hybrid solutions  BizTalk Server 2013, BizTalk Services and the Service Bus are key components for a hybrid solution  Concepts and technology is easy to understand for BizTalk professionals  Microsoft have taken step forward in innovation, but are not there yet 29
    30. 30. Call to action • Build your own VM with BizTalk Server 2013 or provision a VM in Windows Azure • Create your own hybrid solution leveraging the new adapters in BizTalk Server 2013 • Provision a Windows Azure BizTalk Service • Examine and learn from existing examples: • MSDN Code Gallery • BizTalk Server 2013 Tutorials 30
    31. 31. Contact steefjan@msn.com http://www.linkedin.com/in/steefjan @steefjan http://soa-thoughts.blogspot.com 31
    32. 32. Thank you! 32