Download as PDF, PPTX
More Related Content
Similar to Innovating on B2B Connectivity
More from AaronLieberman5
![Getting Started with Apache Spark: Big Data Made Simple [Free Meetup]](https://cdn.slidesharecdn.com/ss_thumbnails/apachesparkgettingstarted-260203175547-8361bcc3-thumbnail.jpg?width=640&height=640&fit=bounds)
Innovating on B2B Connectivity
- 1.
- 2. 1. B2B History 2.B2B Pain Points 3. The Reality of B2B 4. Innovating on B2B - Azure Logic Apps 5. B2B Demo Agenda
- 3. ● Consulting -specializing in integrations and related technologies ● We build connections between systems, applications, people, and ideas Big Compass and Speakers Cloud Practice Manager and Architect Senior Consultant
- 4.
- 5. ● B2B resultedfrom a need for secure and reliable exchange between trading partners ● Electronic Data Interchange (EDI) provided a method for standardized electronic communication ● EDI lacked standards at first ● American National Standards Institute (ANSI) moved to standardize the EDI space ● ANSI X12 was the first to define cross industry formats in the USA while EDIFACT was becoming popular in Europe and Asia B2B History
- 6. ● EDI overthe internet (EDIINT) emerged as the internet became more popular ● With the emergence of the internet, Application Statement 1 (AS1) was created in the 1990s ○ Used SMTP as its means of transfer ○ Allowed large companies to quickly trade documents ● Because IT departments feared AS1 adoption, AS2 was created and based on HTTP communication ● WalMart announced in 2003 that it would implement AS2 protocols with all of its suppliers ○ As a result, AS2 and EDI were widely adopted B2B History: How the Internet Changed EDI
- 7. ● AS3 wasdeveloped due to specific pain points with FTP ● AS3 is not AS2’s predecessor ○ They were built on different protocols for different purposes ● AS4 improves upon AS2 with improved communication over web services and better features than AS2 such as the ability to pull messages B2B History: AS3 and AS4
- 8. ● Trading partnermanagement can be difficult ● Almost always need to speak EDI with B2B transactions ● Must communicate over a variety of different protocols including (S)FTP, AS2/3/4, or even HTTP(S) ● EDI transformations can be more difficult without a tool ● Readability of EDI can make EDI training more difficult ● Scaling B2B and EDI communication B2B Pain Points
- 9. B2B Management, Orchestration,and Processing
- 10. B2B Today ● B2Band EDI are not going away! ● B2B and EDI are growing so we must support B2B implementations ● Often times B2B can’t be communicated using modern protocols like REST
- 11.
- 12.
- 13. ● Codeless drag-and-dropinterface to visually create business processes and workflows ● Quickly integrate with SaaS and enterprise applications with out of the box connectors ● Seamlessly integrate with other Azure services ● Run in a serverless environment to take advantages of scalability, price, and ease of use ● Easily orchestrate steps in a business process ● Automate B2B/EDI business processes Azure Logic Apps Overview
- 14. Azure Logic Apps: A B2B Difference Maker ●Azure Logic Apps provides a serverless B2B solution ○ Makes it easy for developers or functional team members to quickly develop B2B interfaces ○ Azure Logic Apps is scalable ● Ability to communicate over a variety of different protocols including HTTPS, SFTP, and AS2 ● Easily connect to downstream systems using pre-built connectors or an HTTP(S) request ● Easily invoke Azure Logic Apps through modern protocols like REST
- 15. Azure Logic AppsB2B Architecture - Inbound
- 16. Azure Logic AppsB2B Architecture - Outbound
- 17. Azure Logic Apps EDI Setup 1.Set up trading partner 2. Create trading partner agreement 3. Create Azure Logic App for inbound/outbound communication 4. Test the Logic App 5. Run the application in production 6. Log and monitor
- 18.
- 19.
- 20.
- 21.
- 22. References ● EDI history ●AS3 history ● AS2 Protocol ● Azure Logic Apps B2B Setup