2 BizTalk - EDI & B2B Anders Wasén- Enfo Zystems IBM ChampionMikael Håkansson - Enfo ZystemsMVP BizTalkPlease use this slide as your first slide. It means a lot to start and end all presentation generic to give an event a strong identity. Thank you!
3 Kommande events… 12:e Juni Windows Azure Service Bus- Connectivity and MessagingAlan SmithSommar Kollo with Johan HedbergHelsingborg 26:e Juni, Stockholm 27:e Juli + 21:a Aug
5 Agenda What is EDI? EDI history What is it? How to deal with it? EDI FormatsEDI Handling
6 B2B formats – history… EDI (Electronic Data Interchange) What is it? Exchange of any data electronicallyNot dependent of format or transportWhere did it come from?Depends on who you ask…What is it now?X12EDIFACTebXMLRosettaNetxCBLAnd more…Morse telegraph, 1837, USA och EuropaTransatlantic cable 1866Early 1870s, Thomas Edison full duplex two-way telegraph; doubled capacity quadruplex telegraphy 18741902 Worldwide1890 Nikola Tesla, WirelessPopov 1895, struck by lightening during demonstration1935 Baudot, 5-bit code telex -> Telex1960’s ASCII
7 B2B, a brief description Classification? External messages Message standards”Security packaging”Trading partner managementTypical implementation?Various ”platforms”, servers and adaptersMany formats, specifications and no documentationIn short, A MESS!
8 What can we do? Documentation! TPP – Trading Partner Profile TPA – Trading Partner AgreementConsolidation of servers/protocolsExtend SOA to include B2BBreak pure B2B formats in B2B layerWork with external partnersAdd security!
10 B2B formats – X12 ANSI X12 or ASC X12 ANSI - American National Standards Institute (ANSI)ASC - Accredited Standards CommitteeCICA (or Context Inspired Component Architecture)B2B processes as ”reusable” XML entitiesX12 CICA Metadata Interchange Format (CICA-MIF)bi-directional data exchangeRDF (Resource Description Framework) and OWL, a Web Ontology LanguageRDF is a framework for describing resources on the web, e.g. properties for items, content and time schedulesOntology is about the exact description of things and their relationships.Use as a EDI Service Registry and Repository
11 B2B formats - EDIFACT EDIFACT Approved by United Nations 1986 ISO standard ISO-9735Named messages (6 letters), e.g. ORDERS, INVOICTwo releases yearly: D[YY].A and D[YY].BE.g. D96.A (NB! S-releases exist)UNA:+.? 'UNB+UNOA:3+ZYSTEMS:1+DATADIRECT: : 'UNH+SSDD1+ORDERS:D:03B:UN:EAN008'BGM+220+BKOD99+9'DTM+137: :102'NAD+BY ::9'NAD+SU ::9'CNT+2:4'UNT+22+SSDD1'UNZ '
12 B2B formats - EDIFACT Other common standards: ODETTE, European car industryTRADACOMS, retail industryHIPAA, US Health Care Claim Transaction set
15 B2B protocols HTTP/S FTP/S sFTP (SSH) VAN (Value Added Network) Common and recommended:HTTP/SFTP/SsFTP (SSH)VAN (Value Added Network)Common:VPNX.25Less common and NOT recommended:X.400 (Yes, it is still alive)SMTPUSB Stick, print-outs or CD
16 B2B protocols AS1 - Email AS2 - HTTP/S AS3 - FTP/S & sFTP Applicability StatementAS1 -AS2 - HTTP/SAS3 - FTP/S & sFTPAS4 – SOAP/WS (TBD)Based on S/MIMESupports digital certificates and encryptionMessages may request a Message Disposition Notification (MDN)Non-repudiation achieved through digest exchange in MDN
19 EDI Transmission Use a B2B gateway product, e.g. BizTalk What is it? Getting the data across from one Trading Partner to the otherTrading Partners are referred to as ”Internal” or ”External”Transmission is the “sending” of EDITransaction is what is being sentHow to do it?VAN ServicesPackages, protocol bridging, adding security (hopefully), transformationa.k.a. ”Clearinghouse”Use a B2B gateway product, e.g. BizTalk
20 EDI Transmission EDI Acknowledgments X12 Technical Acknowledgment a.k.a. “TA”Is sent if message is received and understoodFunctional Acknowledgmenta.k.a. “997” or “FA”Function stipulated in TPA (remember that “Trading Partner Agreement” document?)Requires validation of the complete message and/or groupAccepted or Rejected status report on the compliance with the “standard”(*)(*) “Standard” = In EDI you have as many standards as there are senders
21 EDI Transmission EDI Acknowledgments EDIFACT Technical Acknowledgment (well, sort of…)a.k.a. “CONTRL”Is sent if message is received and understoodFunctional AcknowledgmentFunction stipulated in TPARequires validation of the complete message and/or groupAccepted or Rejected status report on the compliance with the “standard”(*)(*) “Standard” = In EDI you have as many standards as there are senders
22 EDI Transmission EDI Acknowledgments Synchronous vs. Asynchronous Can be sent either wayX12 more commonly use synchronousEDIFACT pretty much never use synchronousAS2 and AcknowledgmentsMDN is sent either Synchronous or AsynchronousI.e. any EDI Acknowledgments will be sent Asynchronous
23 EDI Transmission History of using FTP transfers EDI batchingBatching is a processing of a bunch of messagesStill very common!History of using FTP transfersSaves money if using a VAN serviceIt’s the way it has always been done…
24 EDI in the future… ebXML xCBL (Common Business Library) RosettaNet XML Based (of course)ebXMLebMS - ebXML Messaging ServicesSOAP/WS based icl. Processes and receiptsISO 15000Collaborative Partner Profile Agreement, CPA DocumentsxCBL (Common Business Library)Open source, EDI basedRosettaNetOpen consortiumMostly TelecomAnd of course EDIFACT and X12!
Your consent to our cookies if you continue to use this website.