on 2018 Mar 06 6:25 PM
Hi PI Experts,
We have a file to file scenario and we are facing an issue in Sender file(FCC) adapter. sender adapter processed partial source file, it seems communication channel picked the file in the middle of it being copied to the source folder and didn't create expected target file.
Is there any settings in sender file adapter(FCC) to handle this issue and avoid to pick partial source file.
However, if we check the archived source file, it is a complete file. I just wanted to know, whether there is a delay for processing and archiving a file.
Please clarify how it was archived entire file and processed partial file.
and let me know, how can we handle processing of partial source file.
Thanks in advance.
Thank you,
Chakradhar
Hi Chakradhar!
Just use MessageTransformBean in sender channel instead of FCC to make use of given parameter.
By the way: according to help topic provided above, using of that parameter is restricted when you use FCC along with "Recordsets Per Message" parameter.
Regards, Evgeniy.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Chakradhar,
If opening the file is not prevented by the operating system, the adapter starts to process the file although it is still being modified. But there is a parameter named "Msecs to Wait Before Modification Check" in the advanced settings of the File Sender channel configuration to work around this issue. This setting causes the File Adapter to wait a certain time after reading, but before sending a file to the Adapter Engine. If the file has been modified (which is basically determined by comparing the size of the read data with the current file size of the input file) after the configured interval has elapsed, the adapter aborts the processing of the file and tries to process the file again after the retry interval has elapsed.
For the complete archive file, it seems the source file has been picked up twice since the file size has changed, and the partial archive file is overwritten.
Anyway, you can use the parameter "Msecs to Wait Before Modification Check" to avoid this issue.
For more details, check the following help:
https://help.sap.com/saphelp_nw73/helpdata/en/44/682bcd7f2a6d12e10000000a1553f6/frameset.htm
Best Regards,
Liz
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Liz,
Thanks a lot for your answer.
The parameter "Msecs to Wait Before Modification Check" is applicable only for the File adapter and it is not available for File Content Conversion (Message Protocol).
Could you please let me know, if we have any other option to handle this issue other than restricting permission at OS level.
Also, if source file picked twice and partial archive file was overwritten then why the target file was not generated again.
Thank in advance.
Thank you,
Chakradhar N
User | Count |
---|---|
78 | |
11 | |
10 | |
10 | |
10 | |
9 | |
8 | |
7 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.