
Robust Cloud integration with Azure
Beschreibung
Alles über E-Books | Antworten auf Fragen rund um E-Books, Kopierschutz und Dateiformate finden Sie in unserem Info- & Hilfebereich.
- Deploy and deliver applications that integrate seamlessly in the cloud and quickly adapt as per your integration needs
- Deploy hybrid applications that work and integrate on the cloud (using Logic Apps and BizTalk Server)
Book DescriptionAny software developers, architects, and technical managers lookng to learn about Azure IaaS essentials need look no further. This book is ideal for Microsoft Enterprise developers, DevOps or any IT professionals looking to connect cloud-based and on-premises systems with Azure.What you will learn - With this book, you?ll learn about: ? Building and supporting highly available and scalable API Apps ? Deploying and delivering applications that integrate and adapt seamlessly in the cloud ? Deploying hybrid applications that work and integrate on the cloud (using Logic Apps and BizTalk Server) ? Exploring new models of robust cloud integration in Microsoft Azure ? Creating your own connector and learn how to publish and manage it ? Building reliable, scalable, and secure business workflows using Azure Logic Apps ? Simplifying SaaS connectivity with Azure using Logic Apps ? Connecting your on-premises system to Azure securely
Who this book is forThis book is for Microsoft Enterprise developers, DevOps, and IT professionals who would like to use Azure App Service and Microsoft Cloud Integration technologies to create cloud-based web and mobile apps.
Alle Preise
Weitere Details
Personen
Martin Abbott is a Microsoft Azure MVP living in Perth, Western Australia. He started his career developing subroutines for commercial computational fluid dynamics software, eventually moving on to more mainstream development and systems integration. He has been working with BizTalk Server since the early days of the product, has spent a lot of time with WCF, but more recently has moved in to providing his customers with integration solutions spanning both on-premises and cloud workloads.Corbould James :
James Corbould has been working in the IT sector since 2003, developing and supporting applications in New Zealand and the United Kingdom. Since 2010, James has been working in the software integration field, designing and building integration solutions using Microsoft technologies such as BizTalk, SQL Server, WCF,.NET, and now Azure, for a wide range of different customers. Recently, he has been working in the health insurance sector and in the building supplies sector.James currently works for Datacom Systems as a consultant and team lead.Morar Mahindra :
Mahindra Morar has been working in the IT sector from 1997, developing Windows and website enterprise applications. In 2009, he has been focusing primarily on integrating systems as a principle integration consultant. Having come from an electronics engineering background, he is able to use this knowledge to design solutions that integrate between wetware, software and hardware.Kumar Abhishek :
Abhishek Kumar works with New Zealand Trade and Enterprise as an integration and data specialist. He is a Microsoft Azure MVP with deep expertise in software development and design. He is a co-author of Robust Cloud Integration and a seasoned contributor to Microsoft blogs, forums, and events. As a technological evangelist, he is specialized in cloud-based technologies such as Azure Functions, Microsoft Graph, Logic Apps, Web API, and Cosmos DB, along with various Software-as-a-Service (SaaS) such as Salesforce, Office 365, and ServiceNow. As a technology advocate, he promotes loosely coupled solution design along with event-based programming.Bhambhani Ashish :
Ashish Bhambhani is an Integration Sr. Premier Field Engineer working for Microsoft. He lives in the Seattle region. He has been working in the integration space for more than a decade. In his current role he helps Microsofts enterprise customers by architecting, designing, building, and maintaining their integration solutions. Recently, he has been able to roll out Azure technologies enterprise-wide for his clients and replace their legacy solutions. He is a content creator and master trainer for some of a Microsofts training that is delivered to clients worldwide. Additionally, he was part of the team that wrote the BizTalk performance whitepaper for msdn.com
Inhalt
- Cover
- Copyright
- Credits
- Foreword
- About the Authors
- About the Reviewers
- www.PacktPub.com
- Customer Feedback
- Table of Contents
- Preface
- Chapter 1: An Introduction to Systems Integration in the Cloud
- What is Azure?
- What is cloud computing?
- Types of cloud platform
- Types of cloud service
- Cloud computing - something old or something new?
- What is integration in the cloud?
- The benefits of integration using the cloud
- Design patterns for cloud integration
- The evolution of integration design and how this applies to the cloud
- Introduction to the microservices architecture
- The evolution of architectures
- Limitation of monolithic application design
- What is microservices?
- The characteristics of microservices
- Types of microservices
- Stateless microservices
- Stateful microservices
- Challenges with the microservices architecture
- SOA and microservices
- Summary
- Chapter 2: What Is an Azure App Service?
- What is an Azure App Service?
- Why use Azure App Service?
- What are Azure Resource Groups?
- App Service plans
- An overview of our sample solution
- Summary
- Chapter 3: Getting Started with API Apps
- Why use API Apps?
- Building, hosting, and consuming your first API App
- What is Swagger?
- Developing and hosting RESTful API App
- Enabling the Swagger UI
- Testing your API
- Deploying ProductAPI to Azure
- Viewing and managing the ProductAPI in Azure portal
- Consuming your API App by generating client code in Visual Studio
- The API App's architecture
- The CORS support
- Enabling CORS in Azure App Service
- Bringing your APIs as-is
- Testing an API using Postman
- Creating a new API App
- Setting up the deployment source for your new API App
- Deploying Node.js API code to Azure
- Security
- What is App Service authentication and authorization?
- Authentication
- Authorization
- Scenario on Authenticating an API App and consuming the authenticated API App
- Summary
- Chapter 4: What is Azure API Management?
- The anatomy of Azure API Management
- API and operations
- Objects within API Management
- Azure API Management policies
- Working with Azure API Management
- Creating your first Azure API Management instance
- Publisher portal and Developer portal
- Importing the API definition through the Publisher portal
- Managing user access rights for Products and APIs
- Customizing the developer experience
- Policies in Azure API Management
- How to use Policies in Azure API Management
- Working with policies in the Publisher portal
- What are the different policies available in the Publisher portal?
- Basic Scenario #1 - Throttle Requests Using a Rate Limit Policy
- Basic Scenario #2 - Rewrite the public facing URI for the GetProducts API operation
- Getting slightly more advanced - Modify default API behavior using conditional statements
- Securing your API in Azure API Management
- Securing your API backend with mutual certificates
- Securing your API backend with Azure Active Directory
- VPN connection in Azure API Management
- Monitoring your API
- Analytics in the Publisher portal
- Logging to EventHub
- Summary
- Chapter 5: Trigger Your First Logic App in Azure
- An introduction to Logic App
- The comparison between BizTalk server and Logic Apps
- Why and when to use
- Diagnosing Logic Apps
- Building your first Logic App
- Create Azure SQL server, database, and table
- Create Logic App and workflow
- Logic Apps using Visual Studio
- Visual Studio 2015 configuration steps for Logic App
- Run Visual Studio 2015 as administrator
- Create Resource group template for Logic App
- Polling Twitter for #SunnyElectricals
- Code view
- Deployment
- Summary
- Chapter 6: Working with Connectors in Logic Apps
- Categorizing Microsoft connectors
- Standard connectors
- Enterprise Integration connectors
- Connectors as triggers
- Types of triggers
- Connector as an action
- Standard Actions:
- Collection Actions
- Building your first connector
- Azure Storage Table connector
- Make your connector work for Logic Apps
- Adding summary and XML Documentation
- Discovering partion keys in the storage table
- Summary
- Chapter 7: Azure Functions in Logic Apps
- The basics of Azure Functions
- Runtime environment
- Bindings, languages, and function types
- Building Azure Functions
- Creating a function
- The structure of a Function App
- Adding complexity
- Adding integration
- Using functions with Logic Apps
- Calling functions directly
- Scenario - Invoice checker
- Other considerations
- Deploying your Function App
- Testing your Function App
- Scaling your Function App
- Monitoring your Function App
- Managing your Function App
- Summary
- Chapter 8: A Deep Dive into Logic Apps
- Workflow definition language
- Parameters
- Output
- Expression
- Operators
- Functions
- Content type in Logic Apps
- Content-Type header
- Text/plain
- Application/json
- Application/XML
- Flow controls, SplitOn, and scope in Logic Apps
- For each loop
- The Do Until loop
- SplitOn
- Switch statement
- Single run instance
- Scope
- Exception handling in Logic Apps
- Scopes to catch failures
- Retry Policies
- The runAfter property to catch failures
- Logic App to update on-premise warehouse with data gateway
- On-premise data gateway for Logic Apps
- Microsoft account prerequisites for installing on-premise data gateway for Logic Apps
- Installation and configuration on-premise data gateway
- Installing on-premise data gateway:
- Creating a work or school identity in Azure Active Directory
- Summary
- Chapter 9: Powerful Integration with SaaS Using Logic Apps
- Exploring the Logic App SaaS connectors
- Hooking up to SaaS solutions using the SaaS connectors
- Working with Dynamics 365 and Office 365
- User authorization using the Salesforce connector
- Salesforce connector - Under the hood
- Leveraging the Salesforce connector: Sunny Electricals automated credit check solution
- Reaching out to the credit check API
- Processing the credit check report using an Azure Function
- Triggering automatic account creation using the Salesforce connector
- Testing the credit check solution
- Hybrid scenarios
- Summary
- Chapter 10: Advanced Integration with Powerful, Scalable Service Bus in the Cloud
- Service Bus types
- Service Bus tiers
- Service Bus Queue characteristics
- Message size
- Time to live
- Dead-lettering
- Sessions
- Retrieving messages off a queue
- Deferring message processing
- Security
- Handling service bus subscription security
- Managing Service Bus outages and disasters
- Service Bus topics
- Subscriptions
- Subscription rules
- Rule filter
- Rule action
- Partitioned queues/topics
- Administration tools
- Scenario
- PremiumInvoice and Invoice topic subscription creation
- Summary
- Chapter 11: Connecting to Event Hubs and an Intr oduction to IoT Hubs
- An introduction to Event Hubs
- Security in Event Hubs
- Event Hub streaming and partitions
- Consumer groups
- Reading from an Event Hub
- Replaying of messages
- Poisoned messages
- Connecting to Event Hubs
- Introduction to Azure IoT Hubs
- Getting started with IoT Hub
- Differences between Event Hub and IoT Hub
- Security in IoT Hub
- The device identity registry
- Shared access policies
- Shared access signatures
- X.509 certificates
- IP filtering
- Monitoring your IoT Hub
- Communicating with IoT Hub
- D2C messaging
- C2D messaging
- Receiving C2D messages
- Processing D2C messages
- Uploading files
- IoT Hub tools
- Device Explorer
- iothub-explorer
- IoT gateways
- IoT Hub protocol gateway
- IoT Hub gateway SDK
- IoT suite
- Scenario - bringing it all together
- Summary
- Chapter 12: EAI/B2B Integration Using Logic Apps
- Enterprise Integration Pack for Logic Apps
- Enterprise messaging in Logic Apps
- Logic Apps Enterprise Integration Tool
- Enterprise Integration Pack connectors
- Enterprise Integration templates
- Building your first Enterprise Messaging solution
- Add partners in your workflow
- Creating a partner within the Integration Account
- Create an AS2 agreements
- Configure your agreement to handle receive messages
- Configure your agreement to send messages
- Store custom metadata information in Integration Accounts artifacts
- Add Metadata information to Integration Account artifacts
- Retrieve metadata from artifacts for logic apps
- Summary
- Chapter 13: Hybrid Integration Using BizTalk Server 2016 and Logic Apps
- Hybrid Integration
- Why Hybrid Integration?
- Maximize use of past/existing investment
- Customer privacy and data security
- Wider audience
- Message exchange pattern
- Datagram or one-way pattern
- Half-duplex or request-response
- Duplex Message Exchange Pattern
- What is a BizTalk Server?
- Azure Relay service
- SB-Messaging Adapter
- Logic App Adapter
- Installing and configuring an adapter in BizTalk Server 2016
- Installing the Logic Apps Adapter in BizTalk Server 2016
- Connecting on-premise BizTalk Server 2016 with Azure Logic App
- Step 1 - Creating Logic Apps for cognitive services
- Step 2 - Typed Polling with the WCF adapter
- Connecting to the Sunny Electricals database
- Creating a two-way send port for Logic Apps
- Connecting Azure Logic App with on-premise BizTalk Server 2016
- IIS configuration for Logic App Adapter
- Consuming a WCF Service in BizTalk 2016
- Creating a Logic App to call BizTalk
- Summary
- Chapter 14: Tooling and Monitoring for Logic Apps
- Tools to monitor Azure resources
- Deployment options
- Azure Resource Management templates
- Parameters
- Variables
- Resources
- Outputs
- Expressions and Functions
- Parameter Files
- Deploying templates
- Creating ARM Template using Visual Studio
- Best practices
- Manual deployments of App Services
- FTP
- MS Visual Studio
- Synch
- Local Git
- Continuous deployment
- Azure Function deployments
- Managing solutions using PowerShell
- Monitoring
- Metrics
- Add metric alert
- Diagnostics settings
- The OMS Portal
- Logic App monitoring
- Run history
- Trigger history
- Logic App message logging with Azure Functions Application Insights
- Summary
- Chapter 15: Whats Next for Azure Integration?
- An integration roadmap for the future
- What and when of Microsoft Azure integration
- Business productivity transformation
- An introduction to PowerApps
- An introduction to Microsoft Flow
- Keeping up with the pace of change
- Final thoughts
- Index
Systemvoraussetzungen
Dateiformat: ePUB
Kopierschutz: Adobe-DRM (Digital Rights Management)
Systemvoraussetzungen:
- Computer (Windows; MacOS X; Linux): Installieren Sie bereits vor dem Download die kostenlose Software Adobe Digital Editions (siehe E-Book Hilfe).
- Tablet/Smartphone (Android; iOS): Installieren Sie bereits vor dem Download die kostenlose App Adobe Digital Editions oder die App PocketBook (siehe E-Book Hilfe).
- E-Book-Reader: Bookeen, Kobo, Pocketbook, Sony, Tolino u.v.a.m. (nicht Kindle)
Das Dateiformat ePUB ist sehr gut für Romane und Sachbücher geeignet – also für „fließenden” Text ohne komplexes Layout. Bei E-Readern oder Smartphones passt sich der Zeilen- und Seitenumbruch automatisch den kleinen Displays an.
Mit Adobe-DRM wird hier ein „harter” Kopierschutz verwendet. Wenn die notwendigen Voraussetzungen nicht vorliegen, können Sie das E-Book leider nicht öffnen. Daher müssen Sie bereits vor dem Download Ihre Lese-Hardware vorbereiten.
Bitte beachten Sie: Wir empfehlen Ihnen unbedingt nach Installation der Lese-Software diese mit Ihrer persönlichen Adobe-ID zu autorisieren!
Weitere Informationen finden Sie in unserer E-Book Hilfe.
Dateiformat: PDF
Kopierschutz: Adobe-DRM (Digital Rights Management)
Systemvoraussetzungen:
- Computer (Windows; MacOS X; Linux): Installieren Sie bereits vor dem Download die kostenlose Software Adobe Digital Editions (siehe E-Book Hilfe).
- Tablet/Smartphone (Android; iOS): Installieren Sie bereits vor dem Download die kostenlose App Adobe Digital Editions oder die App PocketBook (siehe E-Book Hilfe).
- E-Book-Reader: Bookeen, Kobo, Pocketbook, Sony, Tolino u.v.a.m. (nicht Kindle)
Das Dateiformat PDF zeigt auf jeder Hardware eine Buchseite stets identisch an. Daher ist eine PDF auch für ein komplexes Layout geeignet, wie es bei Lehr- und Fachbüchern verwendet wird (Bilder, Tabellen, Spalten, Fußnoten). Bei kleinen Displays von E-Readern oder Smartphones sind PDF leider eher nervig, weil zu viel Scrollen notwendig ist.
Mit Adobe-DRM wird hier ein „harter” Kopierschutz verwendet. Wenn die notwendigen Voraussetzungen nicht vorliegen, können Sie das E-Book leider nicht öffnen. Daher müssen Sie bereits vor dem Download Ihre Lese-Hardware vorbereiten.
Bitte beachten Sie: Wir empfehlen Ihnen unbedingt nach Installation der Lese-Software diese mit Ihrer persönlichen Adobe-ID zu autorisieren!
Weitere Informationen finden Sie in unserer E-Book Hilfe.