Skip to main content
Solved

SFTP Sender Output Filename Issue

  • January 31, 2022
  • 5 replies
  • 723 views

Forum|alt.badge.img+3

How to set-up SFTP Sender connector to ensure output file is finalyzed (content and filename) before it gets copied to SFTP location.

Tried all possible config - it still tries to rename file in SFTP destination.

Here is integration debug log (bold part is something to avoid):

022-01-31 20:00:26,666  57 DEBUG [Integration] ifs.fnd.tc.ftp.SFTP.connect(): HostKey: <removed>
2022-01-31 20:00:27,058  57 DEBUG [Integration] ifs.fnd.tc.ftp.SFTP.connect(): connect() success.
2022-01-31 20:00:27,425  57 DEBUG [Integration] ifs.fnd.tc.ftp.SFTP.dirExists(): Current dir: /COMP
2022-01-31 20:00:27,730  57 DEBUG [Integration] ifs.fnd.tc.ftp.SFTP.dirExists(): Exists: /COMP/TEST
2022-01-31 20:00:27,999  57 DEBUG [Integration] ifs.fnd.tc.ftp.SFTP.dirExists(): Current dir: /COMP
2022-01-31 20:00:28,262  57 DEBUG [Integration] ifs.fnd.tc.ftp.SFTP.dirExists(): Exists: /COMP/TEST
2022-01-31 20:00:28,504  57 DEBUG [Integration] ifs.fnd.tc.ftp.SFTP.upload(): Upload: C:\Temp\ifs_sftp_2187f6745a3fef85_7586108471267687723.tmp -> /COMP/TEST/Pain_bc25032fcb1e8e24.tmp
2022-01-31 20:00:28,508  57 DEBUG [Integration] ifs.fnd.tc.ftp.SFTP.upload(): File size: 2276
2022-01-31 20:00:29,041  57 DEBUG [Integration] ifs.fnd.tc.ftp.SFTP.upload(): Rename: /COMP/TEST/Pain_bc25032fcb1e8e24.tmp -> /COMP/TEST/Pain.001_20220131_200025_CET.xml
2022-01-31 20:00:29,409  57 DEBUG [Integration] ifs.application.messageprocessor.impl.senders.SftpConnectSender.nativeSend(): File 'Pain.001_20220131_200025_CET.xml' has been successfully SFTP transferred to <removed>

Appreciate any tips on this. 

Best answer by BODVARDANS

IFS explained, that SFTP connect sender writes file to SFTP with temporary filename to ensure receiving end does not pick-up file automatically.

There is no possibility to configure this behaviour, so only option is to do a customization.

Closing this topic.

View original
This topic has been closed for comments

5 replies

dsj
Ultimate Hero (Partner)
Forum|alt.badge.img+22
  • Ultimate Hero (Partner)
  • 865 replies
  • February 1, 2022

Hi @BODVARDANS,

 

How does your SFTP sender configuration looks in Setup IFS Connect? Are you using REMOTE_TMP_DIRECTORY?

When using REMOTE_TMP_DIRECTORY, the file will first be uploaded to the temporary directory on the SFTP server. Once the upload has completed, the file will be moved from temporary directory to the location specified in the Connect address, therefore rename would not occur in the sftp location.

 

Hope it helps

Damith

 


Forum|alt.badge.img+3
  • Author
  • Do Gooder (Customer)
  • 3 replies
  • February 1, 2022

Hi Damith,

Thank you for your reply.

 

Sender uses LOCAL_TMP_DIRECTORY.

Using REMOTE_TMP_DIRECTORY is not an option - besides this option uses rename on SFTP as well to my knowledge. 

 

BR, Vardans


Forum|alt.badge.img+3
  • Author
  • Do Gooder (Customer)
  • 3 replies
  • Answer
  • April 7, 2022

IFS explained, that SFTP connect sender writes file to SFTP with temporary filename to ensure receiving end does not pick-up file automatically.

There is no possibility to configure this behaviour, so only option is to do a customization.

Closing this topic.


LevFredrB
Sidekick (Partner)
Forum|alt.badge.img+4
  • Sidekick (Partner)
  • 9 replies
  • April 27, 2022

Hi!
We getting the temporarly name like below “xml.part”. In above examples it seems like it should be .tmp. What decides the name of the temporarly file name when Connect sends SFTP? The remote system in our case demands that temporary file should be .tmp but currently we fail due to it is called xml.part. Can someone explain this, why we seens to get this strange temporarly file name?

 


 


Forum|alt.badge.img+3
  • Author
  • Do Gooder (Customer)
  • 3 replies
  • April 27, 2022

Hi,

Logs are from SFTP Sender using LOCAL_TMP_DIRECTORY. We run it on APPS9 UPD17 version.

IFS clarified, that temporary file is internal mechanics of SFTP sender, therefore cannot be configured in standard.

I tend to think this is due to different version of SFTP Sender, however should be verified with your IFS product support responsible.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings