Processing ebXML Messages
You can process ebXML messages by having the ebXML Module use Trading Networks processing rules to process a message. Whether the ebXML Module processes the ebXML messages using a processing rule depends on how you configure the wm.ebxml.bypassRoutingRule property. If you set this property to false in the ebXML Module configuration file (config.cnf), the ebXML Module will use processing rules. If you do not want to use processing rules, set this property to true, which is the default.
The
ebXML Module provides processing rules for ebXML messages. However, as provided with
ebXML Module 7.1 SP1, the processing rules do not specify any actions on the
Action tab in the
Trading Networks processing rules screen. You define how you want ebXML messages processed by configuring actions for the processing rules. For example, you can create a service you want executed to process messages; then you would use the
Execute a Service action and identify the service you created. For more information, see
Defining Processing Rules.
Trading Networks applies the processing rules after a document recognition process only if the associated processing rules are enabled.
The following lists the processing rules that are provided with the ebXML Module. Based on the criteria in the processing rules, Trading Networks determines the processing rule to use for an ebXML message based on the TN document type of the ebXML message.
This TN document type... | Matches these ebXML messages | Proceed using these processing rules | Whether passed to process management |
ebXML Default | All transport-level messages: ![*](chapterTOC_bullet.png) ping ![*](chapterTOC_bullet.png) pong ![*](chapterTOC_bullet.png) status request ![*](chapterTOC_bullet.png) status response ![*](chapterTOC_bullet.png) duplicate | ![*](chapterTOC_bullet.png) ebXML Ping ![*](chapterTOC_bullet.png) ebXML Pong ![*](chapterTOC_bullet.png) ebXML Status Request ![*](chapterTOC_bullet.png) ebXML Status Response ![*](chapterTOC_bullet.png) ebXML Duplicated Message | By default, not passed to process management if the ConversationID has no value. To set the ConversationID to the Envelope/ Header/MessageHeader/ConversationID, configure the wm.ebxml.defaultDocType.conversationID property to true in the ebXML Module configuration file, config.cnf. |
ebXML Payload | ![*](chapterTOC_bullet.png) A payload containing an ebXML message ![*](chapterTOC_bullet.png) A message-in-error transport-level message | ![*](chapterTOC_bullet.png) ebXML Payload ![*](chapterTOC_bullet.png) ebXML Message in Error | Passed to process management if Trading Networks successfully extracts a conversationID from the message. |
ebXML Error | ebXML error messages; that is, messages that contains an ErrorList element | ebXML Error Message | Passed to process management if Trading Networks successfully extracts a conversationID from the message. |
ebXML Receipt | ebXML messages that contain a deliveryReceipt element Note: The deliveryReceipt element is not present in the ebXML Message Service Version 2.0 Specification. | ebXML Receipt | Passed to process management if Trading Networks successfully extracts a conversation ID from the message. |
ebXML Routing | Multi-hop messages | ebXML Message Routing | Passed to process management if Trading Networks successfully extracts a conversation ID from the message. |