Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

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

Recommended Posts

  • Newbies
Posted

Goodmorning,

Is there somebody who do have some experiences with webservices. We do make our own WSDL's and are willing to use these services in combination with Filemaker Pro.

Locally we did manage to have our WSDL's work in combination with Filemaker 9.xx.

What we really want is:

Having our WSDL's work in combination with Filemaker Server 10.xx in browser (IWP) mode.

So our clients can use our webservices with or without having filemaker.

Our problem is:

We need to know where we have to install or place our (NEXUS) webservices plugin and our WSDL or XML files (webservices) on our server. We are working with an Windows 2003 Server

Known sample what we also are trying to having it work that way is:

http://queen.beezwax.net/fmi/iwp/cgi?-db=Demographics&-loadframes

button: Demographics or Movies

Thanks all!!

Posted

For plugins to work in IWP you need to install them in these places on FMS:

C:Program FilesFileMakerFileMaker ServerDatabase ServerExtensions

C:Program FilesFileMakerFileMaker ServerWeb Publishingpublishing-enginewpcExtensions

Or the equivalent paths on OSX. On OSX keep in mind that you need to set the owner and group of the plugin packages to fmserver:fmsadmin. You will also need to play with the execute privilege or just give owner, group and everyone read/write/execute privileges.

With the plugins in the correct spot you can then enable plugins in the FMS admin console and verify that they load properly.

This topic is 5752 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.