This document summarizes a webinar about processing and delivering real-time data with FME Server. It introduces the presenters and covers topics like event-based and stream-based real-time data, using sensors and geofences for notifications, synchronizing directories to databases, and processing high-velocity data streams. It also discusses demo use cases and polls attendees on their data and notification preferences.

1. How to Intelligently Process
and Deliver Real-Time Data
with FME Server
April 23, 2014

2. Meet the presenters.
Aaron Koning
 FME Server Product Manager
Stewart Harper
 Technical Director, Cloud Services

3. Agenda.
Introduction
Demos
Q&A

4. Ask us. And join the discussion.
Please submit using the
GoToWebinar panel.
We will follow-up with
unanswered questions.

6. What we do.
www.safe.com

7. Poll: What version of FME
Server are you using?

8. FME Server.

9. Strap in, we’re diving deep!
For an introductory overview of our FME product suite check out
the interactive webinar that runs every week on Thursdays:
http://www.safe.com/live-product-demo/

10. What is Real-Time Data?
Data is delivered for processing as it is collected.
On-Demand Real-Time
Complex Event Processing
Low Data Velocity ( < 1 message / second)
Continuous Real-Time
Continuous Stream of Data
High Data Velocity ( > 1 message / second)

11. Event Based Real-Time

12. Event Based Real-Time
(Publishers/Triggers)
Amazon
SQS
Java
Messaging
Service
(JMS)
UDPAmazon
SNSWeb Sockets
Email
schedulerDirectory
Watcher
TOPIC

13. Scheduler
Event Based Real-Time
(Publishers/Triggers)
AWS SQS
AWS SNSWeb Sockets
Directory
Watch
UDP
JMS Email
REST API

14. Event Based Real-Time
(Actions/Subscribers)
TOPIC
Amazon
SNS
Amazon
SQS
Amazon
S3
Email
FTP
Java
Messaging
Service
(JMS)REST APIWeb Sockets

15. Event Based Real-Time
(Actions/Subscribers)
FTP
AWS SQSAWS SNS
Web Sockets
APNS
JMS Email REST API
AWS S3 Google

16. Sensors, Geofences and Notifications
Real Time River Flow Select residents in
affected area.
Send notifications to
residents.

17. Sensors, Geofences and Notifications
Water Data
1. Threshold Analysis
2. Select potentially affected
houses based on flow.
3. Send automated texts
and calls using
Household data

18. Subscribe, report and notify

19. Subscribe
1. User subscribes to an AOI
2. User confirms subscription
3. Load Subscriber
into DB

20. Report, Notify
1. Avalanche incident reported.
4. Send subscribers email
alert
2. Consume Request
3. Select users within
event geofence
Subscribers

21. Mobile Subscribe, Report, Notify
 Mobile data capture (photos, data & location)
 Mobile notifications
 Mobile data analysis

22. Fighting Australian Bushfires with FME Cloud
Success Story

23. Poll: Which notification
methods are most interesting
to you? (select all that apply)

24. Q&A

25. Directory to Database Synchronization
Convert Excel to Google Fusion Tables

26. Directory to Database Synchronization
Convert Excel to Google Fusion Tables

27. Edit and Forget it

28. Edit and Forget it
Immediately update the database after saving

29. Edit and Forget it
Track modified files and the last save timestamp

30. Edit and Forget it
Update the database after all editing is complete

31. Poll: Which file storage services
would you like us to add ‘watch’
capability to? (select all that apply)

32. Stream Based Real-Time
(High Velocity Data)
Engine
Data Stream
Web Socket
TCP/IP
TweetStreamer
JMS
AmazonSQS
Engine
Engine
Engine dedicated to
processing data stream
Engine for other server tasks
Engine for other server tasks
FME Server
Engines
Dedicated Engine
Technology

33. Twitter Streaming
Engine
API WebSockets

34. Stream Based Real-Time
Now add business rules
If:
a threshold number of events
in a given area
within a certain duration
Then:
notify concerned persons

35. Success Story

36. Processing High Velocity Data Streams
Evaluating business rules

37. Processing High Velocity Data Streams
Evaluating business rules

38. Processing High Velocity Data Streams
Geofences and business rules

39. Processing High Velocity Data Streams
Evaluating business rules

40. Processing High Velocity Data Streams
Evaluating business rules

41. Tracking Database
Processing High Velocity Data
Track the reports per zone and time of report

42. Processing High Velocity Data
Analyze # of reports per zone within time period
Tracking Database
If:
a threshold number of events
in a given area
within a certain duration
Then:
notify concerned persons

43. Poll: Which protocol are you most
interested in using with a
dedicated FME Engine?
(select all that apply)

44. FME Server Tutorials and Demos

45. Free FME Server Training
Online instructor lead training:
May 28/29
July 29/30
September 23/24
November 18/19

46. FME Server Technical Webinars
Self-Serve (June 26)
Developing For Data Transformation
(August 7)

47. Raise your hand
to ask a question
over the air.
Please ensure your
audio input is set up.

48. Thank you!
Sales
 info@safe.com
Support
 www.safe.com/support
 (604) 501-9985 ext. 278
Aaron Koning
 Aaron.Koning@safe.com
Stewart Harper
 Stewart.Harper@safe.com