Jump to content

problem importing xml from http


joegold

This topic is 7614 days old. Please don't post here. Open a new topic instead.

Recommended Posts

1) thise networks probably use proxies with authentication. This should be taken care of by the OS & Internet browser, as there is no way of implementing this in filemaker. See below

2) no idea, but try same cure.

Try connecting to you site using the open url script step first. this ensures, internet connection is up & user is authenticated with the proxy. Maybe just set up a page with instrutions like "now press the red button in your fiilemaker solution to retrieve the data..."

Link to comment
Share on other sites

Thanks. I tried adding the open URL script step. The browser window opened no problem, and the internet connection was fine. I switched back to filemaker, and continued with xml import, and it did not work.

The error code I am getting is 718.

Link to comment
Share on other sites

I'm guessing that it is a port problem with the network firewall. Open URL uses the standard port 80 for http connections. Port 80 is usually left open, both in and out, on network firewalls in organizations that allow internet connections.

I think that FileMaker is using either port 5003 or port 2399 to access the xml code. If those ports are not open, then the connection will fail even though opening a web page at the same IP address does work.

Link to comment
Share on other sites

well, try

xml import, http://user:password@myhost:80/fmp?...

This assumes you have configured web companoin to port 80.

If you can view the xml by this url, this should work.

btw.

Before I put up my perl "FileMaker Clone" (see it in sample files), I was putting an XML export on my website. this saves me having to run Filemaker web service 24 hours.

Link to comment
Share on other sites

  • 4 weeks later...

I tried your suggestion: http://user:password@myhost:80/fmp?...

It worked fine on my home computer with no firewall. But when I tried it from the big corporation with the firewall, it gave me the same error #718.

Bummer.

But your second statement makes me wonder if I'm more naive than I think about how this whole xml thing is supposed to work. I've got a database of addresses. I export the records using xml to a file which I upload to my website. Then my customers update their database by importing from the http address that this file resides. Except for my firewall problem, this is working great. Is this the way it's supposed to work? I am not using the web companion at all. I am also not exporting to a http address. I am certainly not providing 24 hour filemaker web service (as you said.) I simply put the file on my website, and they can access it whenever they want. No filemaker server is needed for that. Can someone please let me know if I am missing a big piece to this puzzle?

Link to comment
Share on other sites

  • 3 weeks later...

Hi joegold,

I know, it's been some time:

Since FileMaker 5, it displays XML info when web companion is active. This gives you the same XML as you would have with XML export. Before 6, I had to open the FM url, then save source from Internet explorer to get the XML file. The diff between the static export and web companion XML is that the latter allows for dynamic quieries ...

Link to comment
Share on other sites

This topic is 7614 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.