Skip to Main Content
Serverless Integration Design Patterns with Azure
book

Serverless Integration Design Patterns with Azure

by Abhishek Kumar, Srinivasa Mahendrakar
February 2019
Intermediate to advanced content levelIntermediate to advanced
494 pages
11h 5m
English
Packt Publishing
Content preview from Serverless Integration Design Patterns with Azure

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

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Start your free trial

You might also like

Azure Kubernetes Services with Microservices: Understanding Its Patterns and Architecture

Azure Kubernetes Services with Microservices: Understanding Its Patterns and Architecture

Kasam Ahmed Shaikh, Shailesh S. Agaskar

Publisher Resources

ISBN: 9781788399234Supplemental Content