Hello Rich, it is dangerous (because of possible duplicates) to resend a message with a new ID, therefore this should be avoided. Your WebMethods software should have a way to reset the duplicates check for a given ID (and ideally it should not mark a message as received unless it has actually received the message in a way it is usefull for the application).
I dont know the WM tool, but I know that our software offers you the ability to mark an already received id for "re-receiving" and it also allows already received messages in the archive for reprocessing. It is guranteed that the message is in the archive before the ID is locked (which is the requirmeent of the AS2) - to ensure that exactly your problem will not happen. That said, it would be kind from your Trading Partner to resend the message. If the "EDI" folks refuse to do that (for example because the software does not support it), it is also possible to just ask the ERP folks to resend it. This normally will result in a new transmission ID, anyway. Mit freundlichen Gr��en Bernd Eckenfels Chief Architect -- SEEBURGER AG - Edisonstr.1 , D-75015 Bretten, Germany Fax: +49 (0)7252 96-2400 - Phone: +49 (0)7252 96-1256 mailto:[EMAIL PROTECTED] - http://www.seeburger.de Message: 13 Date: Tue, 2 Nov 2004 21:41:11 -0500 From: "Hurd, Richard [SLCUS]" <[EMAIL PROTECTED]> Subject: EDIINT - duplicate Message IDs/Message Digests? Which is the more common practice (and which is the compliant practice) for EDIINT message failures - resend a message with duplicate Message IDs and Message Digests, or make them always unique? We are receiving duplicates, and our WebMethods installation is refusing to open the payloads because the original message failed (for an unknown reason) and the re-send from the trading partner is a duplicate as far as WM is concerned. The trading partner refuses to resend the document using a different ID and digest, so here we sit; with a payload that is for all intents and purposes useless. The trading partner maintains that "it's standard practice to resend the same message until an MDN is received" and our team is saying of course "we are not so sure resending message IDs and message digests is standard practice in AS2." The finger pointing game begins. Any opinions? All I want is my lousy data. Rich Hurd Johnson & Johnson Consumer Companies IM Planning & Logistics Phone: (908) 874-1523 If you think nothing is impossible, try slamming a revolving door. -- Unknown ------------------------ Yahoo! Groups Sponsor --------------------~--> $9.95 domain names from Yahoo!. Register anything. http://us.click.yahoo.com/J8kdrA/y20IAA/yQLSAA/OIFolB/TM --------------------------------------------------------------------~-> . Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Access the list online at: http://groups.yahoo.com/group/EDI-L Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/EDI-L/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
