At the risk of sounding like a sales pitch one of the key benefits IPNet
provides is the ability to interoperate with other B2B applications -
meaning that an IPNet solution is not required for each and every business
partner. As long as they are using an AS2 or EDIINT certified application,
they should be able to connect with little effort. In addition, support for
Internet standards, multiple XML initiatives and legacy EDI standards gives
each company the flexibility to move to e-business at their own pace.
And now technical questions are being asked:
"Also, how is non-repudiation handled without the VAN?"
this is handled via PKI and digital signatures
"And how does XML make it easier to move data out of an IBM DB2 database?
That data isn't going to morph into XML on its own."
it does not - however, the gist of the article was NOT to say that XML is
the only data format to be exchanged, as Mr. Kammerer observed.
The message is not that EDI is dead, or XML is The King. With IPNet's
solution both formats can coexist, in addition to any other type of data.
Should you have any questions, please feel free to email or call
(949) 476-4455
Bisher M. Ahdab
Product Manager
IPNet Solutions, Inc.
949-838-1026
949-476-4454 fax
www.ipnetsolutions.com
-----Original Message-----
From: jwells123 [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 14, 2001 4:50 PM
To: [EMAIL PROTECTED]
Subject: Re: JB Hunt and EDI to XML (and more) conversion
Question: does IPNet provide all the traditional VAN services like
transaction control, store-and-forward/guaranteed message delivery, and
archiving/auditing?
Also, how is non-repudiation handled without the VAN?
Regarding the article:
"Later, smaller trading partners will be moved onto the network, though some
customers want to keep their EDI links in place because they don't want to
walk away from the managed services a good VAN network can provide, Mangold
admitted."
I can't see why companies would want to take on the role of VAN themselves.
If the services provided by VANs really can be done much more inexpensively,
I'd think the VANs themselves would be doing so to stay competitive.
"Today, integrating with trading partners is a laborious process that
requires J.B. Hunt developers to write CICS Cobol code and tap an EDI
translator to move data out of its IBM DB2 back-end databases."
And how does XML make it easier to move data out of an IBM DB2 database?
That data isn't going to morph into XML on its own.
One other thing I don't understand: why is it supposedly necessary to
perform application-specific development every time a new trading partner is
added? Can't an EDI mapper just map the existing proprietary data format to
the EDI format used by the trading partner?
Sorry if these questions are naive, I don't work in this industry but I'm
trying to deconstruct all the "XML kills EDI" hype.
Thanks!
Jason
----- Original Message -----
From: "Leah Closson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, August 15, 2001 12:57 PM
Subject: Re: JB Hunt and EDI to XML (and more) conversion
> In a previous position (2 years ago), I had a chance to evaluate IPnet's
> "solution" and it is, indeed, a rather slick message
> management/communication package, very flexible and robust, I thought.
> I didn't take a look at the translation portion, as we weren't going to
> switch translators, but what I saw was pretty neat (although for budget
> reasons, not purchased) and was most definitely a VAN replacement, first
> and foremost, I'd say. It would be nice to get some solid info, because
> I am sure the business people who read this article will now be
> expecting even faster monkeys pulled out of ever tighter behinds ;)
>
> Just my 2 cents.
>
> Leah
=======================================================================
To contact the list owner: mailto:[EMAIL PROTECTED]
Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/
=======================================================================
To contact the list owner: mailto:[EMAIL PROTECTED]
Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/
