B2B Integration : A Practical Guide to Collaborative E-commerce

Extensible Markup Language (XML) 183
• Flat File to XML;
• EDI to EDI, e.g., X12 to EDIFACT; and
• Flat File to Flat File (including CSV format type).
The server should support XML standards like xCBL, RosettaNet,
cXML, Open Applications Group (OAG), Financial Information
eXchange (FIXML), Financial Products Markup Language (FPML),
Mortgage Industry Standards Maintenance Organization (MISMO), Open
Travel Alliance (OTA).
FASTENAL — MAKES NEW CONTACTS,
WHILE MAINTAINING THE OLD ONES
Fastenal Co. in Winona, Minn., a decade-long EDI user — thanks to
the demands of its largest customer — the industrial and construction
supplier knew that its existing system couldn't handle XML. Still,
Fastenal needed to accept XML transactions to deal with portals and
dot-coms. In addition, it wanted to unite its more than 600 branch
locations with a common look and feel. And there was that pesky
back-end connection. Seamless integration was of prime importance.
Luckily, Sterling Commerce Inc. had the necessary back-end
connectivity and XML capability. Sterling Commerce is mostly known
for its traditional Gentran EDI products, but it also offers XML
connectivity through some key partners.
This illustrates an important point. Fastenal could have chosen an
EDI/XML product and done the heavy lifting of integration from
scratch. But by researching its needs more fully, the company was
able to frame a better system for its situation. And by carefully
investigating vendors, Fastenal discovered a technology set that would
meet its needs far better and more simply than a homegrown solution.
Source: Condensed from EDI? XML? Or Both?, Part 2, XML in Practice, ITWorld.com.
Eliminate the need for using VAN services
The XML/EDI server should eliminate the need for using Value Added
Network (VAN) services by using the Internet for exchanging