Content Type for EDI Documents that Do Not Contain Mainframe Data
If your client is using HTTP, HTTPS, FTP, or File Polling, you typically will use the application/EDIstream content type. When you use application/EDIstream and Integration Server receives the document, it 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.
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.