Take advantage of FME Server’s capabilities for real-time integration and change data capture. Learn about workflows for monitoring and updating your data as it changes. We’ll look at what data sources/systems are monitored out-of-the-box and how you can enable change data capture for other data sources/systems.
2. FME Server Notification Service lets you
act on events as they happen, and send
information as it becomes available.
Publications and Subscriptions let you
publish to and monitor different systems
and data.
4. Notifications
What they are for
ü A brief message, usually to
trigger an action.
What they are not for
x Transmitting large amounts of
spatial data.
5. Notifications
What they are for
ü A brief message, usually to
trigger an action.
ü Triggering an FME Server
response to an event that
happened outside of FME.
What they are not for
x Transmitting large amounts of
spatial data.
x Triggering an FME Server
response to a continuous
series of messages (many
per second).
6. Notifications
What they are for
ü A brief message, usually to
trigger an action.
ü Triggering an FME Server
response to an event that
happened outside of FME.
ü Sending a message about
something that happened in
FME.
What they are not for
x Transmitting large amounts of
spatial data.
x Triggering an FME Server
response to a continuous
series of messages (many
per second).
x Sending more than one
message per second about
what’s happening in FME.
7. FME Server Notification Service
See the list of what built-in publications and subscribers can be: http://fme.ly/protocols
20. Pros and Cons
Caching whole datasets
ü Easy to set up and
detect changes.
x Need to store entire
dataset - processing
time?
Caching timestamps
ü No storage needed.
x Harder to set up -
variables, datetimes.
Consider: Does my dataset have a timestamp? Can I rely on the timestamp to indicate change?
30. Webhooks
● i.e. Give systems/services
a URL that will respond.
● Send the notification to
FME Server.
● Queue the received
notifications and process
the requests on a
separate thread.
31. Pros and Cons
Database Triggers
ü Pushes right to FME
Server topic.
ü Can push lots of
changes to a holding
table.
ü Perfect for real-time
database changes.
x Database permissions.
Webhooks
ü No need to waste effort
polling.
ü Truly real time.
x Complex to set up.
x Not all systems provide
or accept webhooks.
38. Poll vs. Push Considerations
● Simplicity vs. “real-time”ness
● Can the system push to FME Server?
● Are jobs too long for polling?
● API restrictions for polling?
39. Tip: Use FME Server for
internal systems and FME Cloud
for external systems.
45. Summary
• Polling workflow:
o Change detection + scheduling
• Pushing options:
o Database triggers, webhooks
o FME Server: URL or REST API
• Updating:
o Operations in writer parameters
o SQLExecutor
o HTTPCaller