Hello all.
I have a partner who sends EDIINT documents to us which has the payload of the type text/plain instead of application/edi-x12. Since, submitting the payload to TN doesn’t work in this case, I have created a new processing rule for this partner and developed a service that is called by this processing rule. In the service, I’m using “getConetntPart” with part name as payload, converting it to a string by “bytesToString” and submitting it to the TN using an inbuilt serviuce that we have (This uses wm.tn.doc.xml:routeXml). I’m also sending an MDN back by using wm.EDIINT.rules:processMsg.
When the partner is sending the EDIINT data, I’m seeing an MDN back, but I see an unknown document in the TN. When I open the document, it has all the rest of the EDIINT data except the payload. Interestingly, if I reprocess the inbound EDIINT document in the TN or if I save the pipeline and run the service in my developer, every thing works fine and I see an MDN, and an X12 envelope getting created in the TN. Any suggestions? I’m using wM 6.0.1.
Thanks,
Mark.
#Integration-Server-and-ESB#edi#webMethods