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 AS2 agreements

When two trading partners exchange messages over the AS2 protocol, they generally agree upon a few configurations of the AS2 protocol. Some of these configurations are detailed here:

  • They need to agree upon the AS2 identifiers used in AS2 messages
  • They need to agree on whether they are going to sign messages with a cryptographic signature
  • They need to agree on whether they are going to encrypt messages
  • They need to decide whether they want to send out MDNs after an AS2 message is received
  • They need to decide whether MDNs are generated synchronously or asynchronously
  • They need to decide whether MDNs will be signed or encrypted

Once these configurations are agreed upon, they need to ensure that the EDI engine enforces them. Integration accounts provide the option to store and enforce them through AS2 agreements.

In our scenario, we need to create AS2 agreements...