Default TN Document Types Used by ebXML Module
The WmebXML package provides the following default TN document types:
ebXML Default
ebXML Error
ebXML Payload
ebXML Receipt
ebXML Routing
Note:
The TN document types supported by ebXML Module 6.0.1 are available with ebXML Module 7.1 SP1 to enable viewing of the messages that are persisted from earlier versions.
These TN document types are all instances of the Java class com.wm.estd.ebXML.doc.EbEnvelopeDocType, which extends the Java class com.wm.app.tn.doc.XMLDocType. The ebXML Module sets the following attributes for the TN document types:
The
ebXML Module sets the DocumentID attribute to the MessageID from the ebXML Envelope/Header/MessageHeader/MessageData element.
The
ebXML Module sets the GroupID attribute, by default, to the ConversationID from the ebXML Envelope/Header/MessageHeader/MessageHeader element. You can override this default so that the
ebXML Module uses the CPAId for the GroupID instead. To configure the
ebXML Module to do so, set the wm.ebxml.doctype.groupIDproperty in the ebXML configuration file (config.cnf file) to
cpaID. For more information, see
Configuring webMethods ebXML Module.
After determining the TN document type to use for an incoming ebXML message, the ebXML Module uses the TN document type to form a BizDocEnvelope. A BizDocEnvelope contains the original message and includes additional information that Trading Networks requires for routing and processing the message. In the ContentParts field of the BizDocEnvelope, the ebXML Module saves multiple content parts, the original message as "ebxml", the ebXML envelope as "Envelope", the header element as the "Header", the payloads as the content IDs, and so on.
The ebXML Module sets the User Status to reflect the nature of the ebXML message. The following is a list of all the possible values of User Status:
ErrorMessage
Ping
Pong
StatusRequest
StatusResponse
Acknowledgment
Payload
Receipt
MessageInError
MessageRouting
Duplicate
SendMessage
Persisted