EDI and Software Applications

EDI and JAVA

Java is a programming language originally developed by Sun Microsystems and launched in 1995. While generally compiled to byte code, direct hardware execution of byte code by a Java processor is also possible. Currently, almost all of Java’s software is available under the GNU General Public License. Hence it has become free software. The Java programs most identifiable characteristic is that is platform independent, meaning that it should be able to be written and compiled once, and then be able to be run anywhere.

JAVA script is run on systems worldwide, and while not essential to all system, is intrinsic to many. Java develops Web services using applications and tools within their Web Services Stack. In this stack includes applications such as JAX-WS, JAXB, WSIT, JAXP, and XWSS, which create secure reliable, transactional, interoperable Web services.

Within the EDI environment, which requires a great number of translations, from one format to another in order to make communications understood, Java is present. Java integration with EDI documents is prolific. Products such as EDIReader allow for Java to be parsed bringing it into line with EDI standards.

It is able to be used in XML based systems that have custom SAX parsing. It can support HL7 standard documents, UN/EDIFACT, JDOM and ANSI documents.

It can also turn style sheets into EDI documents. Basically, Java helps to parse EDI documents. There are other products on the market which are translators and Envelope builders for the EDI process. As a translator, the OBOE system parses an EDI/XML file into Java objects. The objects are then used to interact with a GUI or database or some other process such as a web page or batch program.

As an envelope builder, it takes the EDI Objects and Java objects, and builds an EDI document. The EDI document can then be sent via e-mail, to a VAN for transmission, transmitted using a proprietary message delivering system, printed out and faxed - really a wide range of options and what that means is that the Java application separates all the components of the actual underlying “computer talk” of the text, and allows these technical elements then to be able to be represented as other document formats. Thus within EDI, the Java applications allow the EDI documents to be represented through other data formats following translation by the Java application.

EDI and .NET

According to Microsoft, .NET is a service delivery platform that supports business needs and Web service-connected IT. It is basically an umbrella term which encompasses a variety of technologies from Microsoft. The .NET framework is an integral part of the Windows operating system.

It maintains servers to host Web services, development tools to create them, applications to use them, and a worldwide network. It offers a range of Web service technologies that allow users to increase business possibilities by expanding their understanding of how technology can help. This technology is integrated throughout Microsoft products.

.NET is able to map EDI into business objects that can then be used by any .NET programming language such as Visual Basic, C#, Segments, and Data Fields can be mapped directly into objects and properties, for integration with any EDI format.

.NET advertises that it helps organizations get the most out of their technology, while creating new ways to implement other technologies. .NET is a force within the new Net culture, as it enables enterprises to transmit EDI documents.

.NET provides EDI a pathway for EDI to be transmitted through the Internet. The framework is within most Microsoft products, and is required for Widows and Vista applications. The movement of an EDI within the Internet is somewhat different to traditional EDI transmission. While it goes from the sender, it can then be transmitted using Internet protocols such as FTP or HTTP. This allows for a very fast transmission, and can also be encrypted for increased security.