Web Services Manager

Publish your FileMaker scripts as SOAP XML Web Services, which makes it easy to integrate with FileMaker from virtually any other system, programming language, operating system, or hardware.

VersionWhat's New?

Own a license?
Download current version.

Learn more about our
Portfolio License bundle!

Price or Buy Free Download Documentation

Features

Easy to Install

Just copy two FileMaker files and one PHP file onto your FileMaker Server, and you're up and running. No plugins, no client software, no restarts.

Easy to Use

You configure which scripts to publish using a FileMaker-based GUI. Web Services Manager automatically generates the WSDL and handles all of the XML translation.

Universal Access

Read and update your FileMaker database in real time. Instead of being a data island, turn your solution into the hub of your organization!

Included in the Portfolio Bundle

Receive an Enterprise license, which allows for server-side use and unlimited number of users, along with all products from 360Works when you purchase the Portfolio Bundle.

Need help setting up one of our products?

We are experts in FileMaker, Java, and Amazon Web Services. If you need a customized plug-in, modifications to an existing plug-in, or full plug-in/web app integration services, we can perform these services for you. Please fill out our Quick Form and we will contact you to discuss your solution needs and create an estimate.

Video

More About Web Services Manager

The Web Services Manager allows any SOAP ( Simple Object Access Protocol ) compatible software to trigger FileMaker scripts using the industry-standard SOAP XML format. This could include Flash, .NET, PHP, Java, Ruby, Python, C++, or FileMaker itself using the FM Nexus Web Services plugin. The Web Services published by the 360Works Web Services Manager are indistinguishable from any other SOAP server, which puts FileMaker on a level playing field with any other IT solution. Using the 360Works Web Services Manager, you can integrate FileMaker with otherwise incompatible software solutions, and both pull and push information to FileMaker databases.

How Does 360Works Web Services Manager Work?

You use a FileMaker-based control panel to configure which scripts should be exposed, how parameters should be passed to them as input, whether a password is required, and which fields will be returned as the XML result. Tooltips guide you through the process. Once you've configured this, 360Works Web Services Manager will automatically generate a WSDL (Web Services Description Language) describing the available services, which can then be called by any SOAP compatible software.

360Works Web Services Manager is not a plugin. There is no software that needs to be installed on any client machines. Installation consists of nothing more than putting two FileMaker databases on your FileMaker Server and copying a single PHP file to your Web Publishing Engine. After that, you're ready to begin accessing your FileMaker database through SOAP.

System Requirements

All of our plugins are designed to run on Mac and on Windows. All system requirements are the same as those of FileMaker. As long as you meet FileMaker's minimum requirements, you can run our plugins in your Mac or Windows environments.

What does the FileMaker community think?

I whipped up a quick dummy version of what I'm hoping to use the plugin for, and it was incredibly easy to get going, and it all worked fine - getting 550+ records with 8 fields was fast

— David Wikström, CamelCase Data

Their folks have insisted that Web Services, not ODBC or file exchange, be the way to integrate our FileMaker app with their ad production app. So the launch of your product came just in time... In case no one has told you, this rocks.

— Jens Rasmussen, Structure

Web services is such a cool product. I was proud as punch that I could create a WSDL to give to central IT... I felt really pleased with what I had achieved in such a short space of time. Thank you so very much!

— Katy Butterworth, University of Auckland

Read More Testimonials for 360Works

FAQ

  • - B2B integration: Set up real-time access to selected information in your database for customers to access. This could be order info, payment records, inventory levels, project statuses, or any other business-critical information. Use SSL encryption to guarantee security.
    - Medical Groups: An insurance company needs real-time access to a medical group's patient records. Using Web Services Manager, the medical group can provide the insurance company access to its records without the insurance company needing to understand how FileMaker works or how the group stores its data.
    - Advertising Agencies: Manage your advertiser and sales information within your FileMaker database. Your production department can use the Web Services Manager to read sales data or update ad placements using their own production software without having to slow down workflow to unnecessarily learn how to integrate with the FileMaker solution.
    - Enterprise Departments: The 360Works Web Services Manager allows your department to manage its own FileMaker scheduling database while providing the information to the rest of your company in a format which can be easily interpreted by other software solutions.

  • 360Works Web Services Manager is not a plugin. There is no software that needs to be installed on any client machines. Installation consists of nothing more than putting two FileMaker databases on your FileMaker Server and copying a single PHP file to your Web Publishing Engine. After that, you're ready to begin accessing your FileMaker database through SOAP.

  • Web Services Manager is designed with performance and scalability in mind. It triggers scripts by communicating directly with the FileMaker Web Publishing XML gateway, bypassing intermediary layers such as the FileMaker PHP API or FX.PHP. Because of this, there is no maximum limit on the number of records that can be returned by the FileMaker script. It streams the result, which means that it can even return more data than can fit in the available memory of the server that it is running on. It is reasonable to expect anywhere from 2-10 transactions per second under constant load.