Below is excerpts from BizTalk 2009 documentation about new features in BizTalk EDI /AS2 (BizTalk 2009):
Electronic Data Interchange (EDI) is one of the most prevalent means by which businesses exchange data electronically. It represents approximately 75 percent of all business-to-business electronic transactions and grows at about 5 to 7 percent per year. EDI usage entails message syntax and standards (including ANSI X12 and UN/EDIFACT), messaging protocols, and transports.
BizTalk Server 2006 R2 introduced the ability to process EDI messages using EDI pipeline components, as well as AS2 support. BizTalk Server 2009 improves EDI support with the following features:
Dynamic EDI Envelope Generation:
· Override EDI envelope settings at runtime by setting context properties.
· Values configured in party resolution are used unless the specific value is overridden.
· Multiple batch configurations can be created for each party.
· Batch lifecycle can be managed individually.
· HIPAA schemas now support equivalent segments.
Transmitting EDI transactions over the Internet is an increasingly popular alternative to sending and receiving EDI using value-added networks (VANs). Using the Internet for data exchange reduces costs, increases efficiency, and has advantages in terms of redundancy and scalability.
To support this growing trend, BizTalk Server 2006 R2 introduced support for EDIINT AS/2 (Applicability Statement 2). AS/2 is a specification that enables transport of business data over the Internet in a safe and reliable manner. BizTalk Server uses AS/2-defined methods to send, receive, encrypt, decrypt, decompress, sign, and verify signatures between partners using HTTP over the Internet. BizTalk Server helps ensure the security of messages through the use of encryption keys, digital signatures, certificates, and non-repudiation.
BizTalk Server 2009 introduces the following AS/2 features:
· Drummond Group certified for multi-file attachment support, file name preservation support and interoperability.
· Resend messages if an MDN has not been received within a specified time frame.
· Send and receive multiple file attachments.
· Preserve attachment file names.