Skip to Content
0
Former Member
Sep 30, 2016 at 10:47 AM

Attachment File Naming conflicts in SFTP and NFS adapters channels

167 Views

Hi Experts,

We have an existing interface, SFTP-SFTP where the sender channel will look for .xml and respective .pdf file(attachments). If the PDF exists, the sender will send the attachments to the receiver channel(SFTP).

if the PDF of respective XML is missing,then the channel is throwing an error as "missing mandatory additional files", after that no other files are getting processed even if both XML and PDF are found.

SFTP to SFTP scenario file naming conventions:

sender :

test1.xml

test1.pdf

receiver:

test1.xml

test1.xml_test1.pdf

To over come this issue, we are implementing a shellscript which checks for the XML respective PDF, if the PDF does not exist then the XML is sent to a temporary folder and process all the files coming next. (This scripting cant be implemented in SFTP, so we are going for NFS).

After implementing the script in NFs, receiver getting below naming convention.

NFS to SFTP scenario file naming conventions:

receiver :

test1.xml

test1.xml_.pdf

but As per the client requirement, the naming convention to send the PDF file should be test1.xml_test1.pdf. Could you someone help me out in getting the same file name in both scenario's as "test1.xml_test1.pdf" even after implementing the shellscript in NFS.

Thanks in advance,

Vilas