possible cache problem ftp scenario

[michel_dekimpe]

hello,

we have the following scenario

ftp -> ftp

very simple, no integretation rep needed, interface -> none, namespace -> http://none

just pick up the file and put it on another server

strange thing is that the receiver uses for target directory the source directory of the sender to put the file

could this be a cache problem, we cleared the cache but the problem remains

regards,

Michel

[Former Member · Accepted solution]

Hi Michel,

Very strange problem indeed.. not convinced this is a cache problem.. have you checked the cache overview in the Integration Directory ?

If it is a cache problem, deleting, activating and recreating the ftp receiver could solve it.

Using another receiver Business System/Service will surely avoid a cache problem, as an object with a completely different key will be created.

Can you see the correct receiver channel being called in the Message Monitor ?

kr,

Peter

[michel_dekimpe · Accepted solution]

Hello Peter,

Thanks for your reply.

I've already deleted everything and re-created it, no luck.

also we restarted the ftp adapter, no luck

we can see everything is correct untill the system tries to write the file

there he tries to change the directory and it uses the directory of the sender (???)

regards,

Michel

[Former Member · Accepted solution]

Hi Michel

Please make sure Adapter-Specific Message Atributes for Directory for both site Sender and Receiver is not checked.

Regards

Fernand.

[Former Member · Accepted solution]

Hi Michel,

maybe it's a problem in the FTP server, some servers don't work well with PI. So, I've some more questions/hints to help you solve this:

- Is this a productive scenario or still in test ?

- Do you use the same FTP server for sending and receiving in test and production ?

- What brand of FTP servers are you using ?

If you have a test setup using the same FTP server, but the situation in production would be different, maybe you just need to use another receiver FTP server brand..

kr,

Peter

[michel_dekimpe · Accepted solution]

Hello Fernand,

Changing the adapter specific message attributes did the trick.

Only using the fielname was sufficient.

Thanks

Regards,

Michel

[michel_dekimpe]

.