i’m wondering if it’s mandatory to use the service wm.EDIINT:receive (in a customized gateway service) when receiving a message from a partner through AS2?
can we do it just by using wm.tn:receive because we will not be asked to explicitly set the sender(AS2-From), the receiver(AS2-To) and the document type is recognized automatically?
wm.EDIINT:receive handles/understands certain Content-Type / MIME Types which wm.tn:receive can not.
I have a list of the content-types supported in each … will post here soon… need to search my files
another reason (the most important in my opinion) is that EDIINT:receive creates an EDIINT transaction and then sends an MDN if requested. (through some out of the box processing rules and services)
this is the transport level and then comes the business level when the payload is processed.
EDIINT Version 8.2 SP1 process message that have one of the following content types.(These content types are for both EDIINT documents and MDNs.) application/edi-consent
application/edi-x12
application/edifact
application/pkcs7-mime
application/pkcs7-signature
application/xml
message/disposition-notification
multipart/related
multipart/report
multipart/signed
EDIINT Version 8.2 SP1 can process messages with multiple attachments that have one of the following content types:
application/msword
application/octet-stream
application/pdf
application/rtf
application/vnd.ms-excel
application/x-msexcel
application/xml
application/zip
image/bmp
image/jpeg
image/gif
image/tiff
text/html
text/plain
text/rtf
text/xml
EDI Version 8.0 SP1 to process payloads that have one of the following content types:
application/edi-x12
application/edifact
application/xml
application/edi-consent (which you can use to submit TRADACOMS payloads)
Trading Networks Server Version 9.5.1 supported following content types text/xml text/plain
we have EDIINT version 8.0.1.0.31 . and we use wm.EDIINT:receive to handle flat file messages with content type = application/text . we are now facing a problem of MDN sent from WM but not received by the partner although the application/EDIFACT doesn’t encounter any problem.
does this mean that this version doesn’t support the MDN for application/text messages.
Yes, TN shows it sent, there is an EDIINT MDN transaction with user status " SendMDNMsg:DONE" and everything is fine on the activity log.
activity log for EDIINT MDN:
Processing complete
Status changed
Service invoke: wm.EDIINT.rules:sendMDN
Status changed.
Synchronous MDN sent
Status changed. General
Document persisted. General
Routing rule EDIINT Send MDN Message selected
but the partner received a file with an html content (interface wm.tn.route:routeBizdoc , inputs… ) instead of receiving the MDN
please if i can have any help in this probleme : version 8.2.2
actualy we do receive txt and edifact message with ediint receive service (AS2 protocol) : .
the probleme:
we do receive the "stream " of message with content-type: application/edifact , application/txt application/xml but we can not receive messages with conte-type: application/octet-stream
can you tel me if the octet stream is handled by trading network (ediint receive ) …
how can i solve that probleme:
the service that we developped containt does imputs parameters :
protocol
message-ID
contentType
From
To
AS2-From
AS2-To
AS3-From
AS3-To
AS3Filename
stream
ReceiptDeliveryOption
in the flow service we call :
pub.flow:getTransportInfo
and
wm.EDIINT:receive
in the error message when getting message from the new partner we got : missing paramter stream ===> stream is null we do receive no stream
we do have proxy server where we can see that we receive the message with all it content :