Pro&cons of HTTP web service versus FTP interface

[Former Member]

Hi,

We have today a number of file-based interfaces which put a file on the SAP UNIX server and send it via FTP to windows-based applications. One argued today that we should replace the FTP mechanism with some BSP web service which would use the HTTP protocol.

We will also need to keep all the archiving mechanism and the move of unix files between directories.

Is this a really good idea? Pros&cons?

If yes, where should we start to build such Webster? We are running a WAS 620.

Many thanks!

[Former Member]

We kept FTP...

[thomas_jung]

I follow the "if it aint broke, not fix it" way of thinking. So my first question is: are you having problems with the FTP mechanism?

I have both FTP based and WebService based interfaces running at my company. They each have their strenghts and weaknesses. However I don't have any plans to replace the FTP based ones just because I have WebService technology available.

There are several weblogs available on SDN on the subject of WebServices. You might start there. I can say that WebServices are great if you need to cross code pages or need interative type interfaces. However if you need archiving, you will have to build that yourself. If this is batched data and you need an archiving mechanism, FTP may still be the way to go.

[former_member181879]

I would also second Thomas. Never change a winning team. If you are happy with FTP, stick with it.

Cons for BSP: PERFORMANCE! You are moving all files that must somehow land on the disk via the ABAP stack. Also the usual configuration places limits on the file sizes that can be uploaded via HTTP. Did I mention performance?