B2B Integration 10.5 | Administering and Monitoring B2B Transactions | webMethods Module for EDI | Creating Clients that Send EDI Documents to Integration Server | Defining the Content Type to Use
 
Defining the Content Type to Use
The client you create should send the EDI document to Integration Server using the application/EDIstream content type. When you use application/EDIstream, Integration Server passes the document to the Module for EDI content handler as an InputStream. The Module for EDI content handler forms the pipeline with the edidata parameter and assigns this parameter as the pointer to InputStream. Then the content handler invokes the service that the client specifies.
Note: For backward compatibility, Module for EDI also has content handlers to accept documents with the content types application/EDI, application/X12, and application/UNEDIFACT. With these content types, the Module for EDI content handler must convert the document to a String that it places in the pipeline. This can potentially consume a lot of pipeline space and use a significant amount of memory. As a result, it is recommended that you use the application/EDIstream content type because it conserves system memory.
Copyright © 2016- 2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.