There is a network protocol that offers all of these benefits --
Email.
Email, after all, is a file.
It solves a lot of problems; email knows to re-try the connection in case
of a server outage; it warns the sender that it couldn't deliver the
message if it ultimately fails; it's a relatively simple (read: foolproof)
protocol; generally speaking, the file can be sent via plaintext, or it can
be uuencoded if necessary; you can manipulate it with forks and .forward
files and all kinds of tricks to get the file where it needs to go... it
generally responds favorably to return receipts; and it's ubiquitous.
Security is still a question mark, however. I guess you'd have to have some
kind of agreement on how to implement encryption on each end.
What pitfalls does email engender?
> When it comes to document tracking, admittedly, transfers via FTP offer
> nothing in the way of tracking unless both sides have good acknowledgment
> reconciliation procedures in place. Sure, maybe there isn't a nice web
> front-end that allows you to see what has been successfully picked up or
> sent, but then again, if the process was brought back in-house, wouldn't
> that information be available on your own platform (ie: what was sent,
> what
> was/wasn't ACKed, etc.)?
>
> To me, the transport (ie: IP vs dial-up) and the transfer method (ie: FTP
> vs
> "whatever protocol dial-up uses") should really be non-issues. I think
> the
> issue becomes is a third-party (VAN) more practical than direct TP to TP
> connection given that an IP connection (like the Internet) "levels" the
> communications arena?
>
> To address some of your questions:
>
> What if our server is down ?
> The transfer would fail on the sender's end. It would be up to the sender
> to manage this. Really, this would be no different than currently
> managing
> a communications session with a VAN.
>
> Do we use FTP ? If so, what if the partner has a different flavor
> and
> we can't connect ?
> I don't know. Anyone with a good answer?
>
> What kind of problems have people seen when moving away from the
> mothership (VANS) such as resolution of the age ol' problem of " I
> sent
> you a transaction on ... no you didn't ...."
> I would think that it really wouldn't be too different from what is done
> now. If you are reconciling your acknowledgments and have proactive
> procedures to track down unacknowledged documents, it shouldn't be an
> issue.
> If, however, you don't, then it becomes a bigger problem.
>
> Are there security setups that need to be done with every new
> partner
> that wants to send or is it a one time setup of the server ?
> I don't know. Anyone with a good answer?
>
>
> Side question:
> Sterling does offer dial-up connectivity options. We are using a dial-up
> connection right now doing CLEO over an Async connection. Can a VAN like
> Sterling offer the same features/offerings (document tracking, security,
> etc.) that they offer dial-up customers but do it over an IP connection?
> (Maybe the transfer would be FTP, baybe it wouldn't, I don't know. Not
> sure
> if it matters.) It just seems that the majority of our EDI problems tend
> to
> fall in the area of communications.
>
=======================================================================
To signoff the EDI-L list, mailto:[EMAIL PROTECTED]
To subscribe, mailto:[EMAIL PROTECTED]
To contact the list owner: mailto:[EMAIL PROTECTED]
Archives at www.deja.com in bit.listserv.edi-L newsgroup. Use powersearch.
