Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Serverless Integration Design Patterns with Azure

You're reading from   Serverless Integration Design Patterns with Azure Build powerful cloud solutions that sustain next-generation products

Arrow left icon
Product type Paperback
Published in Feb 2019
Publisher Packt
ISBN-13 9781788399234
Length 494 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Authors (2):
Arrow left icon
Abhishek Kumar Abhishek Kumar
Author Profile Icon Abhishek Kumar
Abhishek Kumar
Srinivasa Mahendrakar Srinivasa Mahendrakar
Author Profile Icon Srinivasa Mahendrakar
Srinivasa Mahendrakar
Arrow right icon
View More author details
Toc

Table of Contents (15) Chapters Close

Preface 1. Serverless Integration with Microsoft Azure FREE CHAPTER 2. Azure Functions and Enterprise Integration 3. Introduction to Azure Event Grid 4. Azure API Management 5. Azure Service Bus with Integration Services 6. Introduction to Logic Apps 7. Control Flow Actions and Custom Connectors 8. Patterns with Azure Integration Services 9. B2B/EDI Solutions for Enterprise Integration with Azure Logic Apps 10. Hybrid Integration, BizTalk Server 2016 and an On-Premises Data Gateway 11. Intelligence in Integration Using Azure Cognitive Services 12. DevOps for Azure Integration 13. Monitoring for Azure Integration 14. Other Books You May Enjoy

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...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image