Hi Ken,
Okay let me explain.
As I said, our platform is based on Total-e-Server which is a completely
Java Product. It also depends heavily on XML as the language of
communication and data transfer within the product components.
So the heart of our platform is an application server based on XML. But this
platform is "surrounded" by thousands of connectors (all programmed in Java)
which have only one function; So the platform in itself is application to
application with a central format understood by the heart of the platform
which is XML.
Why do we have integrated XEDI ?
XEDI is for us a Java connector which does only one thing: translate an XML
message in an EDI message and vice versa.
We have customers who want to interact their system with a marketplace. But
they want to have all the orders in the marketplace sent to them in EDI
because they have already all the system in place and working seamlessly.
The objective is to give the partners whatever they want. If they expect
EDI, we will translate the message from XML to EDI;
If partners do not have EDI, we will translate it into the expected format
and will be given to the Universal Listener Framework which will send it
either by email, ...
The idea is that Fortune 1000 companies will still continue with EDI. Our
platform is native XML. This is an advantage for us in terms of web
visualization, ...
We have also developed a connector which will do only one thing. When the
XML message will pass through the platform, to copy the appropriate data and
feed a database. This can give you, in real time, adequate information on
volume of this product orders, etc.... or can feed a business intelligence
tool for analysis;
Hope I have been a little more clear Ken.
With my warmest regards,
Alnoor Dramsi
http://www.korom.net
Paris - France
----Original Message Follows----
From: Ken Steel <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: "Biztalk...I choose you"
Date: Fri, 20 Apr 2001 07:10:36 +1000
Alnoor DRAMSI wrote:
> XEDI is a Java connector translating EDI (EDIFACT, X12, ...) to XML and
XML
> to EDI.
It appears this product would be used to go from EDI to XML at the
sending end and from XML to EDI at the receiving end.
What benefit have you found in doing this? It might appear to the
uninitiated as a rather useless extra step. Why not transmit the
information in EDI syntax instead of going to all the additional
complexity and expense of translating to/untranslating from XML syntax?
What happens when your trading partner expects the communication in EDI
syntax and you send it in XML syntax? Does that force all your trading
partners into this additional complexity and expense also? Where is the
business benefit in doing this?
Ken
--
Ken Steel ICARIS Services
Email: [EMAIL PROTECTED]
Technology: http://www.icaris.net/
=======================================================================
To contact the list owner: mailto:[EMAIL PROTECTED]
Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
=======================================================================
To contact the list owner: mailto:[EMAIL PROTECTED]
Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/
