ebXML Module 7.1 SP1 | Understanding and Using webMethods EBXML Module | Installing and Using ebxml Module | Concepts | webMethods ebXML Module Features
 
webMethods ebXML Module Features
webMethods ebXML Module provides the basic implementation of all major features in the ebXML Message Service Version 1.0 Specification and ebXML Message Service Version 2.0 Specification. The webMethods ebXML Module is built on the webMethods Integration Server and webMethods Trading Networks components and provides the following features:
*Header Processing. When creating the ebXML messages, ebXML Module creates the header elements based on information from the following sources:
*Application that is passed through the Message Service Interface
*Information that governs the message received from the Collaboration Protocol Agreement
*Generated information, such as digital signature, timestamps, and unique identifiers
*Header Parsing. ebXML Module supports extracting or transforming the information from the ebXML Header element into a form that the Message Service Handler (MSH) requires for processing the header.
*Message Packaging. ebXML Module supports the compilation of an ebXML Message envelope, comprising an ebXML envelope, header, and payload, into the SOAP Messages with Attachments container. For more information about SOAP messages, see the SOAP Developer's Guide.
*Security Features. ebXML Module provides digital signature and verification, encryption, and authentication. Other components of the MSH can use these services, including the header processing and header parsing components.
*Error Handling. ebXML Module reports errors encountered during MSH processing or processing of a message.
*Synchronous and Asynchronous Messaging. With ebXML Module, you can employ either synchronous or asynchronous communications to better meet the time requirements of your trading partner transactions. For those messages that require immediate responses over the same Internet connections, you can use synchronous communications. For transactions with longer duration, you can use asynchronous communications.
*Message Persistence. ebXML Module always saves all incoming and outgoing messages in the Trading Networks database.
*Reliable Messaging. The Reliable Messaging feature defines an interoperable protocol for two MSHs to reliably exchange messages. That is, when an MSH sends a message, the recipient MSH receives the message once and only once. Reliable Messaging also handles the delivery and acknowledgment of ebXML Messages. The feature includes message handling for persistence, retry, error, notification, duplicate detection, and acknowledgment of messages that require reliable messaging. Reliable Messaging is achieved when a receiver MSH responds to a message with an acknowledgment. For more information, see HTTP/S Support.
*Message Ordering. The Message Ordering feature allows the presenting of messages to the receiver in a specific order. The receiver MSH forwards the messages in the same specific order to the receiver application for processing the messages. The Message Ordering feature requires the use of the Reliable Messaging feature. For more information, see Message Ordering.
*Multi-Hop Messaging. The Multi-Hop Messaging feature allows messages to be sent from one MSH to another MSH via one or more intermediate parties. This feature allows the next destination of the message to be an intermediary MSH other than the receiver MSH that the original sending MSH has identified. For more information, see Multi-hop Messaging.
*Large Business Document Handling. The Large Business Document Handling allows ebXML Module to send, receive, and process large ebXML messages. For more information, see Large Business Document Handling.
*Payload Compression. The Payload Compression feature allows ebXML Module to compress and uncompress any type of payload in ebXML messages, especially for large business documents. For more information, see Payload Compression.
*HTTP/S and SMTP support. ebXML Module supports HTTPS and SMTP communication protocols along with the HTTP communication protocol. For more information, see Supported Communication Protocols.