ebXML Messaging (also called TRP - Transport Routing & Packaging ) specifically focuses on the means to transmit a document (payload) from one party to another, possibly via intermediaries. This protocol is an attempt to standardize the way B2B transactions are transmitted in a manner which includes all sizes of companies from the Large Enterprise (LE) to the Small & Medium Enterprise (SME).
ebXML-MS does not define the business processes or the content of the messages being sent. ebXML-MS only concerns itself with the secure and reliable transmission of the payload. ebXML-MS Message Service Handler (MSH) sits between the network protocol (SMTP, FTP, HTTP, etc.) and the Business Process at each end. In this way, the MSH is independent of both the transport protocol and the higher level business processes. ebXML-MS can be used to transmit any payload over any network connection.
Optional Test Profiles for ebMS: ebMS Optional Test Profiles represent additional functionality requested by various industry associations and end users. Participation in Optional Profiles is strictly voluntary as software companies enrolled in ebMS interoperability testing are NOT required to undergo any of the Optional Profiles testing. Those software products with version which have undergone Optional Profiles testing are noted on the ebMS Interoperable Products page.
- Automotive Retail Profile >
- XML Encryption Profile >
Links for more information on ebMS:
FAQs on Automotive and ebMS
For more information on the ebXML Messaging standard, please refer to:
http://www.oasis-open.org/
http://www.ebxml.org/
|
