Book Image

Serverless Integration Design Patterns with Azure

By : Abhishek Kumar, Srinivasa Mahendrakar
Book Image

Serverless Integration Design Patterns with Azure

By: Abhishek Kumar, Srinivasa Mahendrakar

Overview of this book

With more enterprises adapting cloud-based and API-based solutions, application integration has become more relevant and significant than ever before. Parallelly, Serverless Integration has gained popularity, as it helps agile organizations to build integration solutions quickly without having to worry about infrastructure costs. With Microsoft Azure’s serverless offerings, such as Logic Apps, Azure Functions, API Management, Azure Event Grid and Service Bus, organizations can build powerful, secure, and scalable integration solutions with ease. The primary objective of this book is to help you to understand various serverless offerings included within Azure Integration Services, taking you through the basics and industry practices and patterns. This book starts by explaining the concepts of services such as Azure Functions, Logic Apps, and Service Bus with hands-on examples and use cases. After getting to grips with the basics, you will be introduced to API Management and building B2B solutions using Logic Apps Enterprise Integration Pack. This book will help readers to understand building hybrid integration solutions and touches upon Microsoft Cognitive Services and leveraging them in modern integration solutions. Industry practices and patterns are brought to light at appropriate opportunities while explaining various concepts.
Table of Contents (15 chapters)

Creating partners in an integration account

Any B2B messages will have sender and receiver IDs in their headers. These IDs, along with some Qualifier fields, uniquely identify a trading partner. Any EDI engine should be capable of reading these header values and resolving the corresponding configuration. To help this kind of partner resolution, we have to create a partner entity. These partner entities must be created for both the host and trading partners.

In the Contoso-SupplyChain integration account, we have to create two trading partners, named Contoso and ShipAnyWhere:

The qualifiers need to be agreed between the trading partners, and they will be used in the EDI messages. The following is our sample EDI header:

Since we are planning to exchange messages over AS2, we will also need to add AS2Identities for both partners. The following screenshot shows that Contoso_AS2...