Professional operation of Safe's FME Flow requires permanent monitoring and observation of the infrastructure at various levels. However, successful deployment must not only be safeguarded in purely operational terms, but also with regard to technical criteria such as the reliable execution of data transformation jobs, which often form the backbone of a geoIT solution. con terra's service.monitor for FME successfully covers the aspects "operation", "logging" and "usage statistics" by aggregating of almost any information that FME Flow emits during operation: i.e. log data, job statistics and engine queues. Based on this information, you get even more value out of FME Flow: for successful operation and satisfied users. The session covers not only everyday operational requirements like getting situational overview on your FME infrastructure but also issues relating to capacity planning for FME flow engines and strategies to understand mid term trends in your job execution.

1. How to manage and optimize
your FME Flow infrastructure

2. Presenter
The
Peak
of
Data
Integration
20
23
Stefan Blume
Consultant
con terra GmbH

3. The
Peak
of
Data
Integration
20
23
So FME Flow is powerful,
but need I to do more?

4. The
Peak
of
Data
Integration
20
23
“Typical”GeoIT setups
• GeoIT solutions are built using different components
• Underlying workhorse: FME Flow
• FME Flow is key to success Geo
software
ETL
IT
processes
Maps &
services
Business
processes
Portals
IT
systems

5. The
Peak
of
Data
Integration
20
23
Focus on FME Flow
● If FME Flow fails →
your business case may too
● If FME Flow is a banger →
don’t become a victim of it’s success

6. The
Peak
of
Data
Integration
20
23
Let‘s get more concrete

7. The
Peak
of
Data
Integration
20
23
Real life examplesand setting
• FMEadmin is running„chains“of FME workspace
executions (dependingon each other)
• Operations
• has good knowledge on assuring systems to be stable,
• may have less knowledge on functional workspace design &
requirements
• Multiple departments are using FME Flow, who cares how
this might affect it‘s capacity?

8. The
Peak
of
Data
Integration
20
23
But there are strategies to assure operational
success!
• Keep track on how your FME Flow performs from an
external viewpoint
• Get transparency on operational data and use it
• Get insights and plan to improve

9. The
Peak
of
Data
Integration
20
23
Tada! Let‘s introduce service.monitor for FME
• Continously check your FME Flow for stable execution
• Provide centralized access to „all data“
• Offer insight gaining statistics and diagrams
• Visualize Engine occupation
• Get notified on any event

10. The
Peak
of
Data
Integration
20
23
Different topics of data
● Monitoring
● Analytics & usage behaviour
● Logging & operational data Monitoring Analytics Logging

11. The
Peak
of
Data
Integration
20
23
Monitoring
● Operational view point
○ Uptime monitoring
○ Engines registered and available
● Functional view point
○ Job has been executed like expected and scheduled
○ Log data is stating a defined pattern

12. The
Peak
of
Data
Integration
20
23
Logging& operational data
● Powerful full text search on all log data
● Quickly investigate on failed jobs
● Understand overall server situation
● Get short term and long term data on job execution and
engine performance

13. The
Peak
of
Data
Integration
20
23
Analyticsand usage behavior
● Understand
○ the overall usage of your FME Flow infrastructure
○ which workspaces fail often or start to fail regurarly
● Solve
○ Conflicts and interdependencies of your job execution
● Plan
○ Better occupation of your FME Engines

14. The
Peak
of
Data
Integration
20
23
Demo

15. The
Peak
of
Data
Integration
20
23
Conclusion

16. The
Peak
of
Data
Integration
20
23
Take aways
● Understandthe importance
of FME Flow for your daily
business
● Ask yourself:What can be
done to improve?
● service.monitoris the
solution to success.

17. Call to Action
1. Come to con terra‘s booth
2. https://www.con-terra.com/servicemonitor-fme
3. Make an appointment

18. Thank You!
s.blume@conterra.de