Manageability of Windows Azure BizTalk Services (WABS)


Published on

Manageability of Windows Azure BizTalk Services is one of the new services on the Windows Azure Cloud platform is BizTalk Services. A service that offers integration and EDI capabilities in the cloud. An important aspect of any cloud service is the manageability aspect. In this session the focus lies on this aspect for the BizTalk Services. How does one manage a BizTalk Services solution, what are the tools and resources in Azure to leverage to get a good overview of the BizTalk Service and it’s solutions. Those questions will be answered in this session and the attendees will learn more about the management side of Windows Azure BizTalk Services.

BizTalk Summit 2014, London March 03-04
Brought to you by BizTalk360

Published in: Technology
  • Be the first to comment

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

No notes for slide
  • What can attendees expect to takeaway from this session:

    Controlling WABS means you have to consider provisioning the right SKU meeting the requirements of your solution, security on premise, BizTalk Service and Bridge Endpoint, deployment, troubleshooting, API, ect.
    There different tools available besides Visual Studio (includes plugins like BizTalk Service Explorer), Fiddler2, PowerShell, Azure Portal en BizTalk Services Portal.
    Managing WABS can be challenging because of the many parts, aspects one must consider.
  • To manage means in my view control. In context of WABS it means control over the service, and its solutions i.e. bridges, agreements, ect.
  • Cloud Advantage: cost effective, scalable infra, easy deployment
    Cloud Challenge: data privacy/isolation, control

    Power is with you as IT Admins
    Scale up/down
    Controlled hotfix and updates rollout (MS)

    Advantages of Managed?
    Creation of environment taken care by Microsoft
    Any infrastructure issues taken care by Microsoft
    Your BizTalk Service is monitored by Microsoft 24/7
    OS updates, security patching on the VMs running your solution is taken care by Microsoft

    You as an admin (customer) deal with the application issues. They are the responsibility of the customer

    Advantages of the model:
    Dedicated compute (no sharing)
    User code isolation
    Message processing security
    Dedicated storage
    Configuration security
    Customized servicing

    Challenge: Management

  • Use case to collaborate with the story on manageability.
  • Walkthrough the business scenario
  • Walkthrough the technical components.
  • Concepts of WABS are there are tools on the left hand side you find tools that provide means of development, deployment and management of the TPM, Bridges, and artifacts. On the right hand side you find the resources in Azure that aid in monitoring, configuration and tracking.
  • Mention the different aspects of management. Out of scope for the story is the governance part for the use case, where one would agree format, protocol, and data.
  • On the high-level, we have the following three personas that interact with the BizTalk service. These personas my overlap in your organization or may be further divided. There’s a IT administrator that deal with creating and managing the service, a developer that deal with application development, and a business admin/consultant that is familiar with the BizTalk Service (B2B) concepts - and deals with creating partner agreements and business processes. He works closely with Developer who design these message and process flows and authors user code as needed, deploys in development environments, tests, debugs and once the application is ready, hands it over to the IT admin for deployment into service.
    If you contrast IT experience with BizTalk server, IT admins would procure machines, setup network, install OS, install SQL and BizTalk Server, and configure them before the application could be deployed. This would take weeks if not months before the application could be deployed on the server. This experience is lot simpler on the Services world. It will take exactly three steps to get the service ready.

    From a Microsoft view there a three persona’s in the real world I reckon one person will perform all the mentioned tasks similar to BizTalk. You hardly see differentiation in roles in small/medium businesses. Only in big enterprises with a large IT department you will see this kind of differentiation. In the end depends on the size of the infrastructure, and implementation.
  • Choose the right SKU regarding your requirements.
    SKU are development, basic, standard and premium.
    Use calculator for cost of SQL Azure, Bandwidth, Storage, Support.
  • Walkthrough the provisioning of BizTalk Service and the environment. After provisioning mention register of BizTalk Service Portal.
  • Security aspect: you have the ACS securing the HTTP(S) Bridge endpoint, self-signed certificate or uploaded new certificate require to securely deploy a solution from Visual Studio and you have security regarding the destination of the messages coming into the bridge. This means security to LOB system (configured through creating LOB target).

    A side note is Windows Azure Active Directory that can play a role regarding security for WABS.
  • Walkthrough the technical components.

    Access Control Issuer Name and Issuer Key for deployment, Services Portal, LOB Target
    Send messages use ACS (HTTP),
  • Deployment of the solution to Azure through visual studio and/or through API backup/restore.
  • Backup the Configuration and Runtime, SSL Certificate, BizTalk Service Settings and some additional items.

    Restore always in suspended state, configure automated backup, target the right environment.
  • Short demo demonstrating the backup of BizTalk Services.

    Snow falls inside the stadium from a hole in the collapsed roof of the Metrodome, Dec. 12, 2010. It was one of many problems during a 6-10 season.

  • Monitoring using the Azure Portal and BizTalk Services Portal. Two distinguished portals one for monitoring traffic and see performance, the other to see messages flowing through the BizTalk Service.
  • Troubleshooting through using the BizTalk Service Portal, BizTalk Services Explorer, Storage (WABSLog). You can look into the tables in Windows Azure Storage, use the BizTalk Service Explorer to look into the tracking data (also possible by using the BizTalk Service Portal). In particular you can look into the WADLogsTable for troubleshooting, or on the LOB side setup WCF Tracing and look into the WCF Trace files.
  • Troubleshooting demo we will look into the various places where you can find information regarding monitoring and troubleshooting. That is WADSlog Table (VS plugin for Azure and look into storage), BizTalk Service Explorer, and BizTalk Services Portal.
  • PowerShell and WABS API (REST)

    Windows Azure provides a REST API that provides the ability to access to much of the functionality available through the management portal and in some cases even more. BizTalk Services has an REST operations ranging from suspend/resume/restart a BizTalk Service to Delete/Backup/Restore a BizTalk Service. Besides the REST API there is are PowerShell scripts (cmdlets) provided through the SDK.

    Cmdlets for LOBRelay, Target and BizTalk Service
  • Demo of WABS API: Custom tool leveraging the REST API and PowerShell demo using the scripts provided through the SDK
  • Wrap up the talk. Recap of the story on management of WABS. As you have seen there a few aspects of managing (controlling WABS), provisioning, security, deployment, troubleshooting, monitoring and the API. There a couple of moving parts of WABS as you have seen and how you provided with the tools can manage it. You have seen where you can find certain parts of information when you have to troubleshoot. There a few sources containing information for purposes of monitoring, tracking and archiving. Combining these sources and present them including means of controlling the BizTalk Services, deployment, ect can be a nice opportunity for Microsoft Partners to build a solution for.
  • Resources online to be found on WABS and management.
  • Manageability of Windows Azure BizTalk Services (WABS)

    1. 1. brought to you by Manageability of Windows Azure BizTalk Services STEEF-JAN WIGGERS
    2. 2. Steef-Jan Wiggers Information Architect at Inter Access/SLTN Microsoft Integration MVP Author Speaker Community Active Runner
    3. 3. Key Takeaways • Learn about the key aspects of managing WABS • Tools and resources • Managing of WABS can be challenging
    4. 4. Manage = Control
    5. 5. WABS Benefits • Customer Focus on Solutions • Scalable, Secure & Reliable Managed by Microsoft • Secure & Isolated environment • Predictable Performance • Better Availability & Control Dedicated Resources • Rich Monitoring & Diagnostics • Business Continuity/ Disaster Recovery Simplified Management
    6. 6. Business Case Payroll service • Connect, transform and deliver • Payroll run Benefits: • Regulatory changes • Different Tax Rules • Reduce cost
    7. 7. Overview WABS Messages in different format containing employee payroll data Messages come from different customers. Multiple protocols: FTP, HTTP, SB Endpoint Bridge Messages get processed and submitted into a LOB system (i.e. ERP or data store) Target/Source Destination Multiple protocols: Service Bus, SQL Server, ... Payroll data
    8. 8. Technical overview Lob Relay (Service Host)
    9. 9. BizTalk Service Concepts Visual Studio PowerShell Portal Transforms Schemas Assemblies Partnership Profiles Agreements Partners Certificates Xml One-Way EDI X12 Pass-Through Xml Request
    10. 10. Management aspects
    11. 11. BizTalk Services roles Design Message/Process flow Develop Application Test Debug Create/Manage Partner Profiles Create/Manage Agreements Create workflows Create/Configure Business Rules Activity Monitoring & Insights Create Service Deploy Monitor Scale Update Business Continuity BizTalk Service
    12. 12. Provisioning • Different SKU’s, different costs - Scaling - LOB Connections - High Availability - Restore/Backup - Number of bridges/agreements - Archiving • SQL Azure/Storage • Bandwidth • Support
    13. 13. Provisioning demo
    14. 14. BizTalk Service Environment BizTalk Service Tracking Database (SQL) Monitoring/ Archiving Store (Storage) Access Control Service (ACS) SSL Certificate Auth Info Access Token Deploy Visual StudioBiz Apps Post message Tracking Info Health & Archive Data https://{servicename} BizTalk Service Creation
    15. 15. Security • Certificate • Access Control Service • LOB Access (BizTalk Adapter Service) - SQL Server - Oracle Db - Oracle E-Business - SAP • WAAD
    16. 16. Security overview Lob Relay (Service Host)
    17. 17. Deployment • Visual Studio to developer environment • Upload resource BizTalk Service Portal or Explorer
    18. 18. Configuration Visual Studio: • Sources and destinations • LOB Target Azure Portal • BizTalk Service BizTalk Service Portal • Partner/Agreements
    19. 19. Backup/Restore • Windows Azure Portal • Configure tab of Service (automation) • WABS API
    20. 20. Backup Operation Log
    21. 21. Backup/Restore demo
    22. 22. Monitoring • Windows Azure Portal • Traffic • Performance • Operations • BizTalk Service Portal • Tracking
    23. 23. Troubleshooting • Tracking • Operations Log • BizTalk Service Explorer • Windows Azure Explorer • WADLogsTable • WCFTrace
    24. 24. Monitoring/Troubleshooting demo
    25. 25. WABS API • Azure REST API • Browser/Fiddler • Custom solution • PowerShell • SDK • MSDN Code Gallery
    26. 26. API demo
    27. 27. Wrap up • Different aspects managing WABS • A couple of moving parts • Tools and resources that can help • Know where to look • Opportunity for partners • Unified Experience for Management
    28. 28. Contact details @steefjan
    29. 29. THANK YOU
    30. 30. Resources • BizTalk Services Documentation • Windows Azure BizTalk Services EAI Bridges – Diagnostics • Managing Windows Azure BizTalk Services with REST API • BizTalk Services Bridges – Troubleshooting • TechNet Wiki WABS • The Enterprise Integration Space • Getting started with WABS