span8
span4
span8
span4
FME technology (FME Desktop, FME Server, FME Cloud) is well suited for working with the latest web technologies.Here you will learn about how to work with:
This is the static data on the web such as images, XML, Shapefiles, AutoCAD DWG, GeoJSON, Web Map Tiles, PDF, and the list goes on.Data that users download and that some web applications consume as well.FME can use all these web resources as well as produce them, and even transfer them to where they are served from.
Accessing
In a workspace, all file-based Readers can accessdata from a URLor Web Resources.TheHTTPCallertransformer can also download data with the added option to authenticate the requests.The HTTPCaller can store cookie data for a host, which allows you to login using one URL and then download a resource from another URL.If the data you download is not XML/JSON, which are easily handled by transformers in FME Workbench, you can use theAttributeFileWriterorFeatureWritertransformers to save it locally, then followed by theFeatureReadertransformer to read it back into the workspace.
Providing
Once you have files, you need to serve them.This can be as simple as copying them to the public folder of a website (e.g.usingFile Copy writer) or you might use an existing cloud service for this purpose.FME has native support for bothAmazon S3and Dropbox (DropboxConnector), and you can upload data to other cloud services such as Google Drive andBox.comusing the HTTPCaller transformer.In addition, thePythonCallertransformer can be used to upload data if all else fails.
Note: Many of the latest web services are implementing an authorization framework called OAuth.In FME 2016, you candefine OAuth 2.0 web connectionsthat the HTTPCaller can use when connecting to web services.This provides greater security than regular HTTP and Token authentication methods.
Examples
Web services provide the standard for means of communication and grant access to functionality between applications that would otherwise be disconnected.FME technology can be leveraged to use existing web services, create new web services, and implement web service standards.FME Server provides web services for some common data workflows and can be extended to implement common industry standards.
FME Server REST API
The FME Server REST API is a powerful tool that can be used to interact with FME Server.TheFME Server REST API Trainingteaches users how to use the FME Server REST API and build their own web applications.The REST API allows a user to interact with the FME Server without the use of the FME Server's Graphical User Interface.This courseteaches users what the REST API is, how to use it, and how to build custom web applications that leverage the power of FME.
Accessing
Native Support
有许多,许多web服务,您可能t to access with FME.Generally, these services either store data for use with a set of applications or process data for use by other applications.FME supports both cases using a combination of Readers, Writers and Transformers.
Web service providers that are natively supported by FME include:
Do-It-Yourself Support
The list of supported providers above is quite small when considering the vastness of the web.To support other web services, the HTTPCaller transformer can be utilized to connect and the required protocol logic can be managed into a single interface, called acustom transformer.
Examples of using the HTTPCaller transformer to connect to web services include:
Note: Many of the latest web services are implementing an authorization framework called OAuth.In FME 2016, you candefine OAuth 2.0 web connectionsthat the HTTPCaller can use when connecting to web services.This provides greater security than regular HTTP and Token authentication methods when connecting to web services such as: Google Drive, Dropbox,Box.com, and many more.
Providing
FME provides a great platform for working with data and FME Server provides a web service for directly exposing data called the theData Streaming service.This service can be built upon to implement third-party web standards as well as creating your own RPC or REST bespoke web services.Web services can be created with FME Server, including native support forData DeliveryandData Loading– two very common web data workflows.
Examples
Webhooks are HTTP (POST, GET) callbacks that are sent to user-defined URLs in response to triggers or events.The use of Webhooks allow for third party data integration with existing services, such as FME Server.Webhooks only need an HTTP URL instead of a specific protocol like JMS or WebSockets.
If your client needs updates for specific events, creating a Webhook for those events will enable them to receive and disseminate information about that event into their automated workflows.A Webhook allows one system to receive data from another system in real-time.Instead of polling a source system for new data, events in the source system automatically send data to the target system.
Using Webhooks is nearly as simple as entering a URL into the address bar of any web browser.The URLs aren’t complicated, usually won’t require any configuration, and there is no requirement to write code!
Accessing or Calling a Webhook URL
TheHTTPCallertransformer is the gateway for FME to integrate with Webhooks provided by third parties.Workspaces, authored in FME Workbench, can translate spatial data and construct messages in the syntax required by other services (e.g.XML or JSON).HTTPCaller can use the POST request method to send the message to the Webhook, where it will be consumed by the third party service.
Providing a Webhook URL
FME Server can provide the Webhook callback URL with its Notification Service.Every topic created in FME Serverautomatically generates a direct URL that can be provided as the callback URL of a Webhook.When an event occurs in another system, the topic in FME Server will be provided with information about that event.
As an example, imagine that you have a webpage where users can post data.You could setup the webpage to forward new entries on to other systems via a Webhook.By providing the Webhook callback URL, and when new data is posted the webpage, the HTTP POST method will send the data to your URL, typically as a JSON payload.This information can be digested to trigger workflows or propagated to other systems using subsequent Webhooks.
Subscriptions can be configured to monitor a topic and thenFME Server can perform additional events, such as delivering data via email or updating a database, based on the protocols you have set up.
Examples
WebSockets are a relatively new technology, implemented on top of HTTP, that allows for bidirectional browser-based client-server communication without the overhead of polling (AJAX requests with HTTP overhead), nor the inconvenience and unreliability of client plugins.Modern browsers include built-in implementations of a JavaScript API for connecting to a WebSockets server.Web applications can use WebSockets to pass information back and forth between server and client to give an always connected, real-time, and immersive feel.
Since the 2014 release,FME Server can act as a WebSocket serverwithout additional modules, allowing fast real-time communication with client web applications, with minimal setup required.
Accessing or Receiving
Using theWebSocketReceivertransformer, FME can receive WebSocket messages from various servers.A feature is produced each time a message is received, and the contents of the message is placed into the specified attribute.FME workspaces containing WebSocketReceiver transformers can be authored to process the messages in the same workflow to create spatial data or for generating notifications based on data contained in the message.
Messages can also be received by theWebSocket Publisher– part of the FME Server Notification Service.This publisher receives messages over TCP from a WebSocket-supported client and publishes them to FME Server topics.客户可以包括WebSocketSender支持 transformer, as well as Java or HTML5 web browsers.
Providing or Sending
TheWebSocketSendertransformer can send messages to WebSocket servers.The first input feature will cause the WebSocketSender to initialize a connection, and features specified in the data to transmit will be sent to the server, including the first feature that initiated the connection, in real-time.
TheWebSocket Subscribercan be used to receive notifications from the FME Server Notification Service and publish them over TCP to WebSocket-supported clients that are connected to the FME Server WebSocket server or another target URL.Supported clients include the WebSocketReceiver transformer and HTML5-based web browsers.
Examples
Tutorial: Creating Web Services using FME Server
Data Loading Options With FME Server
See your Salesforce.com accounts on a map
Streaming features from PostGIS to FME using WebSockets
WebSockets and FME Server (2014)
WebSockets and FME Server (2015)
FME Server as a WebHook for littleBits
Using a Link, URL or POST as a Source Dataset (FME Server 2012 )
© 2020 Safe Software Inc |Legal