we have followed the instructions in “8-2-SP1_Trading_Networks_Concepts_Guide.pdf” document, we invoked “wm.tn.doc.ff:routeFlatFile” in the gateway service to receive flat file documents.
however we need that a synchronous MDN being sent to the sender like what the service “wm.EDIINT:receive” does for EDI inbound messages (EDIINT transactions).
Are you saying that your partner is posting EDIINT directly to your gateway service? If they are posting to the wM built-in service (your URL:port/wm.EDIINT:receive), the MDN will be generated automatically like it is for any EDIINT document. Then, if your payload is not EDI or XML, the userProcessPayloadService is invoked which calls your custom gateway service.
Actually, in the gateway service handling flat file messages, i’m mapping the “contentStream” variable to ffdata input of “wm.tn.doc.ff:routeFlatFile”. the only transaction generated is the one related to my flat file document type. the content of this transaction does not include any header (just payload).
here you are talking about the header as if i’m using the service wm.EDIINT:receive. i wish i could use this service but it didn’t work with flat file message since FF content-type is application/text (not application/edifact).
i’m getting a little bit confused, should i use “EDIINT:receive” or “tn.doc.ff:routeFlatFile” is enough regarding MDN requests.