Quantcast
Channel: SCN : All Content - Process Integration (PI) & SOA Middleware
Viewing all articles
Browse latest Browse all 7030

Default Seeburger message splitter configuration

$
0
0

We have a scenario in which we need to be able to ignore EDI messages from partners prior to receiving official confirmation and then setting up the partner in the Seeburger message splitter.  If we receive files from partners before we complete the message splitter configuration, the sender channel keeps trying to process the same file and continually fails during the split, essentially blocking the channel from processing the files we need to process.  We are using the SAP file adapter for this scenario. 

 

I've read the "Default Configuration" section message splitter guide and tried setting up "DEFAULT" splitter configuration.  I did so by copying the splitter configuration for a valid partner and then simply changing the name, the sender name, and the mapping name to "DEFAULT" and left the rest the same.  I did so for both accepted and partly accepted.  The sender channel still complains:

 

     "Error: Error in Adapter call failed. -module:MessageSplitter failed. MESSAGESPLITTER:No configuration found for the source file ..."

 

What is the proper default configuration?  It seems that my intention for the default configuration is exactly what it is meant for.  Is my understanding incorrect?


Viewing all articles
Browse latest Browse all 7030

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>