As mentioned earlier, we “…enveloped a single tset type (e.g. 850s) in one pass.”
The wM 6 EDI adapter docs describes its approach to batching quite nicely. Our approach was quite similar, though we queued the docs before translation whereas the EDI adapter has you queue the docs after translation. The high-level steps we used:
- Queue the XML doc in a public q. We have 1 q per doc type per partner.
- A scheduled delivery task gets created when you define each q. When kicked off, we process up to a max number of docs from the q.
- The process translates each XML doc to EDI and then adds the group and interchange envelopes.
- You don’t have to do it this way, but we put the EDI string inside an XML envelope and submitted that to TN. A custom delivery service extracts the EDI string and delivers it via HTTP or FTP, depending on the partner config.
HTH.
#Adapters-and-E-Standards#webMethods#Integration-Server-and-ESB