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 an X12 agreement

In B2B messaging, both trading partners need to agree upon variants of the messaging protocols, such as X12 and EDIFACT. The following are a few configurations the trading partners should agree upon:

  • The EDI format, such as X12 or EDIFACT
  • The version of the protocol standards; for example, X12 has versions ranging from 00100 to 00700
  • The EDI sender and receiver IDs used in the EDI messages
  • The kind of acknowledgments generated; for example, functional or technical acknowledgments

All these can be defined in X12 or EDIFACT agreements in an integration account.

In our scenario, Contoso is not making use of X12 connectors. As such, we don't have to create an X12 agreement for Contoso. However, on the ShipAnyWhere side, we will create an X12 agreement called ShipAnyWere_Contoso:

In the Receive Settings, leave all the options as they are by default...