Peers,
I have encountered some interstng / frustrating problems in posting documents (X.12 4010 997) to TN. Appreciate help here
I have a flow service to poll a directory to read the content of flat files, which contains EDI X.12 4010 data, and then the flow service will will call another flow service (EDI Main Process Flow Service) to process the EDI data (which call API in the back end system) and generate FA (which the EDI Main Process Flow service will call routeXML to deliver to TN) .
The issues that I have is
-
I call the routeXML to deliver the generated FA to TN. However, I found that if I have more than 1 file in the directory to be processed, the FAs posted to TN will always be the 1st one generated. I have traced both flow services and pipeline and I found that the generated FAs are correct (i.e. based on the content of individual EDI file read) before calling the routeXML.
-
If I use the flow service to poll the directory, read the EDI flat file, and then call my other flow service (EDI Main Process Flow Service) to process the EDI file, the generated FA will be posted to TN via routeXML and TN recognizes the document as X12 4010 997 no problem. However, if I use another flow service which read the data, then post to TN directly (via calling routeXML), and then configure a processing rule in TN to call the EDI Main Process Flow Service, the calling of back end system API is correct and a document (assumes to be the FA) still posted to TN, but TN does not recognize the document as X12 4010 997, instead the content part of the document is named as bytes and seems to contain all the pipeline information
Any ideas
Appreciate help here. Really Urgent
#Integration-Server-and-ESB#B2B-Integration#webMethods