VFP 9: Help with sending/receiving XML via FTP

Hello,

Looking for resources which will help me understand XML via FTP. The same
application is used by both the sender and recipient.

Here is what I do (sender):

Insurance claim is created (single record).
The record is converted to XML.
The XML file is uploaded to specific FTP directory for the specific
insurance company.

At the other end (recipient):

Recipient checks FTP folder for contents.
Recipient is prompted to download the claims.
The claims are downloaded and exported to table.
Confirmation is returned to sender.

I have the concept of how it will work, but I need a good book or
suggestions from you on how to actualy deploy the idea.

Thanks for the input.

JD

Villi
Wed Aug 09 10:15:51 CDT 2006

John Dandy wrote:

> I have the concept of how it will work, but I need a good book or
> suggestions from you on how to actualy deploy the idea.
> Thanks for the input.


First, have a look at VFP's help in the section regarding XMLTOCURSOR and
CURSORTOXML.
Second, are you sure FTP is the best way to go? That way you'll need to have
both the server and the client expose a FTP directory and accept ftp traffic
over it.
So, why not create a webservice which the client simply calls (sending up
the data in xml format) and which responds to the client with a flag
indicating whether the operation completed with success? This way you'll
have only the central-server acting as a server (and only on port 80/http)
and the clients won't need to be ftp-servers, they would just need a
connection with port 80 open (which is the typical open door also behind a
firewall).
To call webservices, all you need is VFP and SoapToolkit 3.0 (free from MS).

BTW: anybody knows other freeware tools (as is SoapToolkit3) to invoke SOAP
webservices from VFP?
--
Villi Bernaroli
Studio K s.r.l.

Thomas
Mon Aug 14 08:23:16 CDT 2006

John Dandy schrieb:
If you don't like the WebService-Approach from the other post
I'ld look into sending the XML via email - you get
protocolling and perhaps some easy rule based behaviour on the receiving
side (depends on the setup used there) and better security since no
directory is exposed.

You might also look into encrypting the XML if it is for
insurance/financial data.

my 0.02 EUR

thomas

John
Thu Aug 24 13:06:59 CDT 2006

Thomas,

It seems web service would be overkill for what I'm attempting to do.

Each user on the system would have their own unique FTP login and directory.
The VFP application connects to the FTP server and directory for the user.
Once connected, XML files are exchanged.

One potential problem would be a user logging onto the server with FTP
client. Once connected with his login and password, he could navigate other
user directories and might even cause some damage.

The information is not so sensitive that data encryption would be necessary.

Based on the security built the VFP application and how it connects to the
FTP server and the risks of someone connecting with FTP client, would you
still recommend email?

Thanks,
John

Thomas
Fri Aug 25 02:30:58 CDT 2006

John Dandy schrieb:

> It seems web service would be overkill for what I'm attempting to do.
Thought so - but sometimes tackling a problem with a slightly
"overcharged" solution teaches a bit - you are certain you are fit for
other probs afterwards.
>
> Each user on the system would have their own unique FTP login and directory.
> The VFP application connects to the FTP server and directory for the user.
> Once connected, XML files are exchanged.

ANY server is a slight risk - it depends on the calibre of the admin and
the OS used.
>
> One potential problem would be a user logging onto the server with FTP
> client. Once connected with his login and password, he could navigate other
> user directories and might even cause some damage.

IMHO security aspects are better controlled by email approach.
Especially if you have to give access to more than a handful of people -
remember the risk is 1 - (1-risk1User)**Nuser. The result often
surprizes when calculated.
>
> The information is not so sensitive that data encryption would be necessary.
Hint from someone in the same industry in germany - think about it, play
around with it, if you happen to read about it, get your brain into
"working mode" to remember better. Be prepared to answer the coming
questions - I have seen too many setups where security was slapped on in
a hurry. I think no security would be better than some of the easy
breakable things, as it gives a false sense of security.

>
> Based on the security built the VFP application and how it connects to the
> FTP server and the risks of someone connecting with FTP client, would you
> still recommend email?
Yupp. Technology in itself is so used that "administration" can be
handled by almost anybody - less need for admin knowledge. Security
level much higher, much of the intended fuctionality (ACK, protocol)
already built in. The metaphor is probably closer.

Enough pre-built code on the vfp side availabe. A well rounded (although
perhaps a bit dated) overview of possible technologies is in megafox by
Akins,Kramek &Schummer, where you find also some base classes solid
enough to grow upon. Recommended, if you don't have a familiar starting
point already: you save many H checking out the different routines
available and have more surrounding commentary than any possible
routine. And the technology hasn't changed that much - it is often sold
only under a different name <g>.

We have Webservices and email integrated, and the email parts are always
easier to handle <g>. For instance we use different email recient
adresses for different marketing campaigns and each agent sends back his
answer on participation, number of leads asked for and so on. We
identify the agent by parsing the automatically created email text -
so there is no need to create a couply of thousend return adresses.
YMMV here, but the originating adress helps a lot if anything goes
wrong. You still can search along the entire mail slot tree...

my 0.04 (I've done it <g>) EUR

thomas

John
Fri Aug 25 15:48:27 CDT 2006

Thomas,

Thanks for the response. Email sounds like the better/easier solution.
What would you reccomend for learning material, especilly how to handle
email and attachments from within VFP?

Thanks!
John