260 likes | 392 Views
Våra sponsorer. BizTalk - EDI & B2B . Anders Wasén- Enfo Zystems IBM Champion. Mikael Håkansson - Enfo Zystems MVP BizTalk http://blogical.se/blogs/mikael Twitter : @ wmmihaa. Kommande events…. 12:e Juni Windows Azure Service Bus- Connectivity and Messaging Alan Smith
E N D
BizTalk - EDI & B2B Anders Wasén- Enfo Zystems IBM Champion Mikael Håkansson - Enfo Zystems MVP BizTalk http://blogical.se/blogs/mikael Twitter: @wmmihaa
Kommande events… 12:e Juni Windows Azure Service Bus- Connectivity and Messaging Alan Smith SommarKollo with Johan Hedberg Helsingborg 26:e Juni, Stockholm 27:e Juli + 21:a Aug
Agenda • What is EDI? • EDI history • What is it? • Howto deal with it? • EDI Formats • EDI Handling
B2B formats – history… • EDI (Electronic Data Interchange) • What is it? • Exchange ofany data electronically • Not dependentof format or transport • Wheredid it come from? • Depends on whoyou ask… • What is it now? • X12 • EDIFACT • ebXML • RosettaNet • xCBL • And more…
B2B, a briefdescription • Classification? • Externalmessages • Message standards • ”Securitypackaging” • Trading partner management • Typical implementation? • Various ”platforms”, servers and adapters • Many formats, specifications and no documentation • In short, A MESS!
Whatcanwe do? • Documentation! • TPP – Trading Partner Profile • TPA – Trading Partner Agreement • Consolidationof servers/protocols • Extend SOA toinclude B2B • Break pure B2B formats in B2B layer • Workwithexternal partners • Addsecurity!
B2B formats – X12 • ASC X12 (Accredited Standards Committee) • a.k.a. ANSI X12 • Created 1979 • Numbered messages (transaction sets), e.g. 850 (Purchase Order), 810 (Invoice) • Using “version” and “release”, e.g. Version 4 Release 1 (typed as: 004010) ISA*00* *00* *08*9251750000 *08*1234567890 *030627*1304*U*00401*000001403*0*P*>~ GS*PO*8019721193*1234567890*20030627*1304*1403*X*004010~ ST*850*01403001~ BEG*00*SA*548177**20030627~ REF*AN*547794~PER*BD*JOHN JONES*TE*5552225555~ ……. SE*30*01403001~ GE*1*1403~ IEA*1*000001403~
B2B formats – X12 • ANSI X12 or ASC X12 • ANSI - American National Standards Institute (ANSI) • ASC - Accredited Standards Committee • CICA (or Context Inspired Component Architecture) • B2B processes as ”reusable” XML entities • X12 CICA Metadata Interchange Format (CICA-MIF) • bi-directional data exchange • RDF (Resource Description Framework) and OWL, a Web Ontology Language • RDF is a framework for describing resources on the web, e.g. properties for items, content and time schedules • Ontology is about the exact description of things and their relationships. • Use as a EDI Service Registry and Repository
B2B formats - EDIFACT • EDIFACT • Approved by United Nations 1986 • ISO standard ISO-9735 • Named messages (6 letters), e.g. ORDERS, INVOIC • Two releases yearly: D[YY].A and D[YY].B • E.g. D96.A (NB! S-releases exist) UNA:+.? ' UNB+UNOA:3+ZYSTEMS:1+DATADIRECT:1+20051107:1159+6002' UNH+SSDD1+ORDERS:D:03B:UN:EAN008' BGM+220+BKOD99+9' DTM+137:20051107:102' NAD+BY+5412345000176::9' NAD+SU+4012345000094::9' CNT+2:4' UNT+22+SSDD1' UNZ+1+6002'
B2B formats - EDIFACT • Other common standards: • ODETTE, Europeancarindustry • TRADACOMS, retailindustry • HIPAA, US Health Care Claim Transaction set
B2B - ArchitecturalOverview Internet Firewall Intranet DMZ Messaging B2B Gatway BizTalk ERP Messaging Messageflow EDI Message ORDER Message XML ORDER (Enrichment) XML ORDER
B2B protocols • Common and recommended: • HTTP/S • FTP/S • sFTP (SSH) • VAN (Value Added Network) • Common: • VPN • X.25 • Less common and NOT recommended: • X.400 (Yes, it is still alive) • SMTP • USB Stick, print-outs or CD
B2B protocols • Applicability Statement • AS1 - Email • AS2 - HTTP/S • AS3 - FTP/S & sFTP • AS4 – SOAP/WS (TBD) • Based on S/MIME • Supports digital certificates and encryption • Messages may request a Message Disposition Notification (MDN) • Non-repudiation achieved through digest exchange in MDN
AS2 – Applicability Statement 2 AS2 Signed/ Encrypt EDI Internet XML Order DMZ Firewall Messaging B2B Gateway Package MDN De-envelope Verify Match Transform
EDI Transmission • What is it? • Getting the data across from one Trading Partner to the other • Trading Partners are referred to as ”Internal” or ”External” • Transmission is the “sending” of EDI • Transaction is what is being sent • How to do it? • VAN Services • Packages, protocol bridging, adding security (hopefully), transformation • a.k.a. ”Clearinghouse” • Use a B2B gateway product, e.g. BizTalk
EDI Transmission • EDI Acknowledgments • X12 • Technical Acknowledgment • a.k.a. “TA” • Is sent if message is received and understood • Functional Acknowledgment • a.k.a. “997” or “FA” • Function stipulated in TPA (remember that “Trading Partner Agreement” document?) • Requires validation of the complete message and/or group • Accepted or Rejected status report on the compliance with the “standard”(*) (*) “Standard” = In EDI you have as many standards as there are senders
EDI Transmission • EDI Acknowledgments • EDIFACT • Technical Acknowledgment (well, sort of…) • a.k.a. “CONTRL” • Is sent if message is received and understood • Functional Acknowledgment • a.k.a. “CONTRL” • Function stipulated in TPA • Requires validation of the complete message and/or group • Accepted or Rejected status report on the compliance with the “standard”(*) (*) “Standard” = In EDI you have as many standards as there are senders
EDI Transmission • EDI Acknowledgments • Synchronous vs. Asynchronous • Can be sent either way • X12 more commonly use synchronous • EDIFACT pretty much never use synchronous • AS2 and Acknowledgments • MDN is sent either Synchronous or Asynchronous • I.e. any EDI Acknowledgments will be sent Asynchronous
EDI Transmission • EDI batching • Batching is a processing of a bunch of messages • Still very common! • History of using FTP transfers • Saves money if using a VAN service • It’s the way it has always been done…
EDI in the future… • XML Based (ofcourse) • ebXML • ebMS - ebXMLMessaging Services • SOAP/WS basedicl. Processes and receipts • ISO 15000 • Collaborative Partner ProfileAgreement, CPA Documents • xCBL(Common Business Library) • Open source, EDI based • RosettaNet • Openconsortium • Mostly Telecom • And of course EDIFACT and X12!