360Works AutoUpdate, how to test server is up prior to calling DB

[RodgerBell]

For a time yesterday the autoupdate.360works.com site was down.  (Did not respond to ping) This caused calls to the auto update DB to hang when launching several of our DBs (3-5min).

 

What is the proper way to call the autoupdate.360works.com/AutoUpdate360works DB in a FM script?  Is there a way to check that the domain is active before calling an external data sources in a filemaker? 

[Joe Pampalon]

Hi Rodger,

 

I've implemented the method outlined here: http://www.soliantconsulting.com/blog/2012/10/testing-whether-database-available-filemaker-server

 

You can access the page by going to "http://autoupdate.360works.com/connectionTest/test.php". This page will respond with "connected" if the AutoUpdate360Works.fp7 database is available and "out of luck" in any other situation. You can test if the database is up by setting a web viewer to the connectionTest URL.

 

I will be implementing this on our AutoUpdate 12 server by the end of the day. You can test with FMP 12 using the "Insert from URL" script step.

[RodgerBell]

has this been updated to allow for Filemaker 13?

 

We recently upgraded and this auto update functionality seems to be broken.

 

Edit: never mind just looks like the URL has changed:

 

new: 

 

fmnet:/autoupdate12.360works.com/AutoUpdate360Works

 

Seems to work