Use of Seeburger Classifier withour splitter?

Question

Hello,
Can you please let me know if we can use Seeburger Classifier without splitter?
if this is possible,can you please suggest relevant links which explain such scenario?
Than

Answer 1

Hi Shweta,
It's a little while since I've used Seeburger but I seem to remember the following, which I hope will help you.
Seeburger Classifier creates an attachment by the name of the "attName" parameter you submit to the Classifier module.  If you do not submit an "attName" parameter value, the Classifier module will use a default value.  You can see the classifier attachment in SXI_MONITOR - it is simply a set of information about what the Classifier determined about the message.
Where the Seeburger mapping module parameter setting is mappingName=AUTO (instead of a static mappingName of the a single mapping, e.g. mappingName=AnsiX12_812_V4030) it will attempt to use the classification xml attachment which was (in the case of where you specify mappingName=AUTO) expected to be have been created earlier in the module chain - again, if no classifierAtt parameter value is specified to provide the name used for the Classifier module's attName (attachment name) then I believe Seeburger mapping module uses the default.  I think the default behaviour of Seeburger mapping module when using mappingName=AUTO is also to split by default, and creates the FunctionalAck in place of the whole message.
I believe there are two solutions to your problem (without getting into developing AF modules):
The first, and easiest, way to get Seeburger mapping module to not produce an Ack and to map 1-to-1, is to leave the Classifier module out of the chain and to specify your exact mapping in order for it to perform a 1-to-1 mapping.  In order to do this you will need to know what file is coming in on your Sender channel.
The second way is that there is a "split" parameter (true/false - true by default for AUTO), and (if I remember correctly) a splitMode parameter too.  The long and short of it here though, is that the ability to support these parameters' usage to enable 1-to-1 mapping on a mappingName=AUTO will be down to your master (e.g. AnsiX12_Company, EDIFACT_Company, TRADACOM_Company) mappings which are used to then branch out to the per-instance mappings which are message name/version specific (e.g. AnsiX12_810_V4010, EDIFACT_ORDHDR_V9).  If using these parameters does not automatically get your 1-to-1 mapping working, you may require some consultancy from Seeburger to enable the 1-to-1 mapping for Classifier driven mapping - I seem to remember this not being a very straightforward process.
Kind regards.