File adapter ping: Is it writing temporary files to the target host (selftestxxx.javatemp)?

[former_member212578]

Hello community,

I have a question regarding the ping channel functionality for the file adapter in the communication channel. The "ping" for the file adapter seems to do more than just a network ping. Among the entries in the pop-up is also one statingy "Directory writability test succeeded".

Does the "ping" also write files to the destination? Background for my question is that we found two files selftest4084751.javatemp  and selftest4084750.javatemp on our target host for the ftp channel and want to find out where they are coming from.

Thank you for your feedback

Mark

[former_member212578]

Hello community,

we could actually reproduce the behaviour and it is indeed the manual file adapter ping which is writing test files to the target. It only occurs when the adapter is used as receiver and in FTP mode.

The adapter is writing a selftest<node id>.javatemp file for each of the Java nodes (communication channel instances) to the target host. It tries immediately afterwards to delete them but in our test the deletion even failed and the files remained.

All other parameters don't seem to have an influence on the ping directory writability. Also the connect mode "permanent" doesn't execute a writability test for keep-alive purposes.

We tested the file adapter 6.40-7.31, the SAP SFTP adapter and the Seeburger SFTP adapter.

Results are as following:

Adapter	Version	Direction	Connect Mode	Ping
File	640	Receiver	Permanent	selftest<node>.javatemp
File	640	Receiver	Permanent (2h waited)	No writability test (no ping manually executed)
File	640	Receiver	Per File Transfer	selftest<node>.javatemp
File	731	Receiver	Permanent	selftest<node>.javatemp
File	731	Receiver	Per File Transfer	selftest<node>.javatemp
File	-	Sender	-	No writability test
SFTP (SAP)	-	Receiver	-	No ping (as of SP01)
SFTP (Seeburger)	-	Receiver	-	No writability test

So please be careful when doing the ping to security critical communication partners :-).

Mark

[former_member212578]

Hello Kalyan, hello Sri,

thank you for your posts . Actually we have the temp file feature and I checked but the file is created as XI_<msgid>.xml. This feature hasnt written the mysterious selftest*.javatemp files.

Regarding the ping I am not so sure. It does the following two tests (ping for file receiver channel 6.40):

Destination Directory Writability Test		Directory "/..." is writable
Receiver Agreement Existence Test		Binding exists with interface ".." and namespace ".."

What does the adapter do to test the Directory writability? We've actually been assuming it does wrote selftest*java files and immediately deletes them.

Thank you for further feedback

Mark

[former_member186851]

Hello Mark,

What does the adapter do to test the Directory writability?-It check whether the folder exists and it is writable(Necessary permissions)

[former_member186851]

Hello Mark,

Ping channel doesn't write any files. It just checks whether channel is connected to target directory/path and writable.

For the temp files you can check as suggested by Kalyan.

[Former Member]

Hello Mark,

No Ping Channel does not write any temporary files in the Target FTP Directory.

Please check if you are using the 'Use Temporary File' in the Processing parameters. If yes, change it to Directly.

Thanks,

Kalyan