Web Services
Web Services Plug-in functions can be executed from the server, but are triggered by a script schedule rather than user interactivity. This means you typically need to set up a queue table in the solution that holds the necessary parameters for making requests. Then a scheduled script can check the queue for new items and run the appropriate functions.
Server-based execution is generally not appropriate where immediate feedback to the user is required.
When using the plug on the server it is best to load WSDLs from a URL using the _FmNx_Load_WSDL_From_URL function.
Note:
When debugging on the server if you are using the verbose setting make sure that you have set the file path to a directory that the server has write access to.
Also, when using plug-in functions on a FileMaker Server from a scheduled script, you will need to call _FmNx_Register every time the script runs.
Note that to load the plug-in on the server, you need to stop and start the Database Server after installing the plug-in in the correct directory.
Comparing Server-based execution and Client-based execution
For server-based execution, web services requests are made by the FileMaker server, and made available to all clients. The down-sides to this are
a) the data must be stored at least temporarily on the FileMaker server to make it available to the clients, and
b) it is not an immediate process. The client must add a record to a request queue table, the FM server must use a script check the queue every minute for any new records, make appropriate web services requests to the provider, then store the responses, which the clients can then see.
For client-based execution, the plug-in must be installed on every client, and the client makes a direct connection to the web service provider. The response to the client is immediate, and only data that you need to store and share can be saved to the FM Server. This is also easier to develop, since no server queue is required.
For client-based execution, the plug-in must be installed on every client, and the client makes a direct connection to the web service provider. The response to the client is immediate, and only data that you need to store and share can be saved to the FM Server. This is also easier to develop, since no server queue is required.
/groups/ws/search/index.rss?tag=hotlist/groups/ws/search/?tag=hotWhat’s HotHotListHot!?tag=hot0/groups/ws/sidebar/HotListNo items tagged with hot.hot/groups/ws/search/index.rss?sort=modifiedDate&kind=all&sortDirection=reverse&excludePages=wiki/welcomelist/groups/ws/search/?sort=modifiedDate&kind=all&sortDirection=reverse&excludePages=wiki/welcomeRecent ChangesRecentChangesListUpdates?sort=modifiedDate&kind=all&sortDirection=reverse&excludePages=wiki/welcome0/groups/ws/sidebar/RecentChangesListmodifiedDateallRecent ChangesRecentChangesListUpdateswiki/welcomeNo recent changes.reverse5search
Comments