on 01-23-2016 9:13 AM
Hi,
I have a requirement where I need to process the huge volume messages. So I decided to choose split the records through Recordset per message option in sender file adapter.
But my source structure have Header,1,Detail,*,Footer,1
And my target structure have Detail,* without Header and Footer.
How do I config the sender channel and let me know whether recorset per message will support even in nested structure also?
Because when I test with dummy scenario structure like Detail,* for both sender and receiver, Recorset per message is working.
I have declared the channel like below.
Recordset Structure: DETAIL,1
Recordset per messsage: 1
If I use the structure like Header,1,Detail,*,Footer,1 it's not working.
Please help me to setup the configuration to split the messages.
Regards
Arun
Hi Arun,
If you mention recordset structure as Header,1,Detail,*,Footer,1 then entire file contains only one record set structure so the entire file will come as one message, You can mention the Recordsset structure as Detail,1 and give Recordsets per message as per your requirement then file adapter will split the file into multiple messages, check below FCC configurations.
In the mapping you can apply below logic to your Detail node then Header and Footer records are not part of target message.
Regards,
Praveen.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Arun,
Recordset per message will work for nested structure as well.
But in your case you can handle this in mapping.
Don't map header and footer nodes
And in the receiver Channel maintain as
Record Structure : Detail
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
81 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.