August 2003
Intermediate to advanced
624 pages
15h 3m
English
Content preview from Using XML with Legacy Business ApplicationsBecome an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
Start your free trial
Version 1.1 Requirements
Functional Requirements
I don't have many ideas at this point, but a couple come to mind.
Native data exchange capability: Performing file format conversion is essential to many electronic commerce scenarios. However, it is worthless unless you can also move the data around. Building in a native capability for transmitting and receiving data would save users from having to do their own integration with a suitable utility. The top candidates for file transfer and packaging protocols might be FTP, HTTP, SMTP, S/MIME, ebXML messaging, EDIINT AS1/AS2, or SOAP (more about these in Chapter 13). The primary network protocol that should be supported is IP (for the public Internet). However, there may also be a need in some situations ...