Creating an EDI Client
To send documents to Integration Server to be processed through Trading Networks, you create a client. The client can use one of the following transports to send the EDI documents:
HTTP or HTTPS
FTP
File Polling
File Polling is a feature of Integration Server that allows your client to drop the document into a directory that Integration Server monitors. When documents arrive in the directory, Module for EDI can process them.
EDIINT AS1, EDIINT AS2, or EDIINT AS3
If you want to use EDIINT to transport your EDI documents, use Module for EDIINT and Trading Networks. For more information, see webMethods Module for EDIINT Installation and User’s Guide.
The rest of this section describes clients that use HTTP, HTTPS, FTP, or File Polling.
When your client sends the EDI document to Integration Server, it must associate the document with a content type that Module for EDI recognizes, for example, application/EDIstream. When Integration Server receives a document that has an EDI content type, it passes the document to the appropriate EDI content handler. The EDI content handler performs initial processing on the document, which includes creating the pipeline with the edidata variable that contains the EDI document. After performing the initial processing, the EDI content handler invokes the service that the client specifies, that is, the wm.tn:receive service, to have Trading Networks process the document.
For more information about how to create the client, see webMethods Module for EDI Installation and User’s Guide.
