webMethods EDI Module IntroductionThe webMethods EDI Module (EDI Module) enables business partners to exchange EDI documents within and across the extended enterprise, providing comprehensive EDI support as a key part of the webMethods total business process automation solution. The EDI Module provides services and transformation management tools that enable you to recognize, transform, convert, validate, and map multi-transactional EDI documents in real-time or in batch. The following table shows the capabilities of the EDI Module based on the components you use: EDI developers can use the WmEDIsamples as a reference. 2) WmEDIforTN package. and IS document types that demonstrate how to use the EDI Module and webMethods Developer to execute typical EDI processing scenarios. you should delete the WmEDIsamples package.Architecture When you install the EDI Module. mappings. and 4)WmEDIsample package. . Before going into production. Note: The WmEDIsamples contains sample EDI flow services. four packages are installed into the Integration Server: 1) WmEDI package. 3) WmEDIINT package. EDI Module in a production environment is comprised of the following three packages: The WmEDI package It is the basic functionality that provides support for the EDI standard to the webMethods Integration Platform. Documents using the EDIINT protocol are processed through Trading . strategic partners) and marketplaces to form a business-to-business trading network. The EDI Module uses the functionality of Trading Networks to provide additional features. suppliers. Trading Networks It is a webMethods component that enables your enterprise to link with other companies (buyers.Integration Server It is the underlying foundation of the webMethods Integration Platform. which is a standard for how to transport documents. This interaction allows you to use Trading Networks as a gateway for EDI document exchange. and batching the sending of EDI documents. reconciling FAs. The WmEDIforTN package It allows for the interaction between the WmEDI package and Trading Networks. The WmEDIINT package It adds support for the EDIINT exchange protocol. such as support for VANs. flow services. the EDI Module processes the documents using the functions of the other the EDI Module packages (WmEDI and WmEDIforTN).g. They are processed based on logic you define in Trading Networks. after Trading Networks performs its processing. At run time. you must use Trading Networks. the EDI Module provides the transport logic only and does not process the documents.. you must use Trading Networks. After you design the process models. XML or custom format) documents.. As a result. . The process run time facility of the Integration Server executes the business processes (conversations) at run time. if you want to use the EDIINT protocol. you generate them to create the run-time elements (e. triggers. 2) When non-EDI documents use EDIINT.) that reside in the Integration Server. You can use EDIINT for both EDI and non-EDI formatted (e.g. etc. 1)When EDI documents use EDIINT.Networks. it can pass documents to the process run time to perform the logic that you designed in a process model webMethods Monitor It allows you to monitor the progress and status of the business processes (conversations) involving EDI documents. ! webMethods Modeler It is a design-time tool that you can use to create process models that define how to include EDI documents in business processes (also called conversations). webMethods Monitor interacts with the process run time to obtain the status information. To use the process management facility of the Integration Server for EDI documents.