On the compression note - depending on your mode of transport with this partner they may be able to compress it before they encrypt it. I've heard most "way larger marketers" use the AS2 RFC over HTTP/HTTPS which includes methodology for compressing the files before they are encrypted. All products supporting the AS2 RFC (should) support the included compression portions. In most of the AS2 Products I'm familiar with it is a simple matter of checking the "compression" option in the trading partner agreement setup.
The compression for AS2 can dramitically reduce the time it takes to process a file because instead of decrypting a 30 MB file it is only decrypting a 3 MB file. Andy Merrill --- In [email protected], "Hurd, Richard [SLCUS]" <[EMAIL PROTECTED]> wrote: > Hi, > > We are using Trading Networks to bring EDIINT data from a WAy Large MARkeTer > into our translator. The size of the file is approximately 30MB. This > file is encrypted and it takes approximately four minutes for our platform > to process it and send an MDN back. > > The problem is that this WAy Large MARkeTer has its timeout for MDN receipt > set to 2 minutes... and if they don't receive it, they resend the 30MB file. > Every half hour. For four days, or until it is updated as 'received' on > their web site. > > The first time it happened, we received over 50 copies of this file before > we realized what was going on. Now we know, and we can catch it and flag it > on that merchandiser's web site as being received; but that's a poor > solution to what should be a simple problem to fix. > > We have tried to get them to (a) compress the file; (b) wait for a piddly > little 4 or 5 minutes rather than two for an MDN; (c) or break out the file > because it's acutally a bunch of ST/SE groups within the interchange. > > Currently the answers are No, No, and No; and > by-the-way-here-you-go-it's-been-half-an-hour-have-another-file. > > I'm loath to simply change something in webMethods, or stamp my dainty > little foot and ask for a patch. Any change in the volume of this > transaction is going to negate any coding changes that we do in Trading > Networks to fix this issue. It should be fixed at the source, but we're > having difficulty with traction (not that we had any illusion that it would > be easy.) We are continuing efforts on that front, however. > > However, due diligence forces me to ask: is this a Trading Networks > problem? Is there someone with that kind of experience? I'm trying, but my > expertise is Gentran and all those little pictures of coffee cups and stuff > in webMethods Developer get me way confused. > > Thanks. I'm pretty stumped at this point. > > > > [Non-text portions of this message have been removed] . 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/
