FME Flow Fundamentals for Admins: Setup & Configuration FAQs
0 likes750 views
The document outlines FME Flow fundamentals for administrators, including setup and configuration FAQs. It covers the architecture, deployment options, automation capabilities, and hardware recommendations for effective implementation. Additionally, it highlights user authentication types and necessary maintenance requirements to ensure successful operations of FME Flow in various environments.
FME Flow Fundamentals for Admins: Setup & Configuration FAQs
- 1. FME Flow Fundamentals for Admins: Setup & Configuration FAQs
- 2. Merline George Technical Support Specialist, FME Flow Chris Berger Customer Solutions Team Lead Sanae Mendoza Technical Support Specialist, FME Flow
- 3. Welcome to Livestorm. A few ways to engage with us during the webinar: Audio issues? Click this for 4 simple troubleshooting steps.
- 4. Agenda 1 What is FME? 2 Aspects of Architecture Pre-Install 3 Deployment Options 4 FME Flow Engine Types 5 Basic Hardware Recommendations 6 FME Flow Configuration with Esri 7 Resources to set up SSL 8 Maintenance & expertise requirements 9 User Authentication types 10 Q+A Session Agenda
- 5. Today… Learn to set your FME Flow deployment up for success with expert guidance for a smooth, efficient setup from start to finish.
- 6. Poll: What is your top concern when configuring FME Flow?
- 7. FME Flow offers streamlined solutions. With the right guidance, you can ensure a smooth, efficient setup every time!
- 9. FME Flow Hosted Safe Software managed FME Flow The only All Data Enterprise Integration Platform FME Form FME Flow The Authoring environment workspaces are built here. The Deployment environment delivering services to your organization. FME Enterprise Integration Platform Platform Overview
- 10. Event Driven Real Time FME Flow Apps - Submit Jobs and Trigger Automations - Stream or Download Job Results FME Flow Automations - Polling Services - Email Received, FTP/S3/Directory Modified, etc. FME Flow REST API - Job as a Webhook Stream Processing - Dedicated Engine(s) run a continuous job - Native support for message brokers FME Flow Automations - Push Services - Webhook/Message Received, Topic Notified, etc. FME Flow: Automation Capabilities
- 11. FME Flow Automations Automating Processes with FME Flow Automations ● Event-driven workflows ● Eliminate manual intervention ● Remove schedule-based delays ● Ensure data is always current and available
- 12. Automating Processes with FME Flow Workspace Apps User uploads file to FME Flow Workspace App
- 13. 1 2 3 Unlimited, Managed Users - User/Role permissions - Authentication Services (AD, SAML) Flexible Engine Deployment - Deploy Engines Anywhere - CPU-Based Pricing - Remote Engines Advanced Engine Management - Queues & Job Routing - Active Periods - Engine Assignment FME Platform Overview
- 14. Customer Story City of Naperville Project Automating time-consuming processes for their Electric, Public Works, Finance, and Water departments. Solution Integrating FME with Cityworks to automate service requests and work orders. Results ● 3300+ service requests and work orders automated, saving hours of manual effort. ● Three staff with specialized coding skills free to focus on high-value tasks rather than manual work ● Increased collaboration and stronger relationships between departments “With FME, we were suddenly saying “yes!” to other departments and implementing requests quickly. Now, we’re viewed differently in our interactions. FME makes it easy for us to improve our relationships with other departments by helping improve their business processes.” - Danielle DuBose, Database Developer, City of Naperville
- 15. Automate Workspaces Schedule Jobs No-Code Workspace Apps Process IoT Data in Real Time Published FME Workspace Files (.fmw) FME Form Author Unlimited Managed Users Monitor System Performance Administrator FME Flow
- 16. Poll: How familiar are you with FME Flow?
- 17. “What key aspects of the architecture should you understand before installing FME Flow?”
- 18. FME Flow Architecture FME Flow is comprised of several components, each performing a different function.
- 19. Core Controls job routing, scheduling, and resource allocation. Manages communication between all components. Engines Executes FME workspaces (jobs). Processes data transformations and sends results to the Core. Database (Postgres) Stores job history, system settings, and user data. Tracks jobs, schedules, and system state.
- 20. Web Application Server (Apache Tomcat) Provides the web interface and API access for all users. Manages user authentication and security. System Share Shared file storage for data, workspaces, and temporary files. Ensures data accessibility for all components.
- 21. FME Flow Architecture ● Flexible: Deploy together or apart. ● Customizable: Bring your own components. ● Scalable: Add Engines and power.
- 22. “What are the different deployment options?”
- 23. Pros Cons ● Simple setup ● Lower cost ● Minimal maintenance ● Fast deployment ● Some scalability ● Single point of failure ● Limited scalability ● Performance limitations ● Not suitable for high availability
- 24. Pros Cons ● Scalable ● Resource optimization ● Flexible ● More complex setup ● Higher infrastructure cost
- 26. Pros Cons ● High availability ● Load balancing ● Disaster recovery ● Resilient ● Most complex setup ● Higher infrastructure cost ● Requires advanced technical knowledge
- 27. Deployment Pros Cons Express ● Simple setup ● Lower cost ● Minimal maintenance ● Fast deployment ● Single point of failure ● Limited scalability ● Performance limitations ● Not suitable for high availability Distributed ● Scalable ● Resource optimization ● Flexible ● More complex setup ● Higher infrastructure cost Fault Tolerant ● High availability ● Load balancing ● Disaster recovery ● Resilient ● Most complex setup ● Higher infrastructure cost ● Requires advanced technical knowledge
- 28. Deploy FME Flow in any environment. FME Form & FME Flow On-Premise Multi-cloud / Hybrid Contain- erized Cloud Hosted FME Flow with Remote Engines (deployable anywhere) Docker & Kubernetes Fully hosted FME Flow on AWS
- 29. Due to its flexibility, ease of configuration, constant updating, and development, FME is an ideal tool supporting and accelerating everyday work in the processing and validation of spatial and non-spatial data. Marek Szczepkowski Project Manager, Visimind
- 30. Resources ● ● Visimind is saving PSE hundreds of hours of processing time - FME by Safe Software
- 31. “What are the differences between FME Flow Engine Types”
- 32. Standard Engines Fixed licenses that are purchased per engine. Available to run jobs for the duration of the license period. FME Engine Types
- 33. CPU-Usage (Dynamic) Engine(s) that are licensed by CPU time (credit based). Available to run jobs for the equivalent credit hours. FME Engine Types
- 34. CPU-Usage (Dynamic) Engine(s) that are licensed by CPU time (credit based). Available to run jobs for the equivalent credit hours (based on CPU + System time). 1 Credit = 1 hour of CPU Time FME Engine Types
- 35. Standard Recommended Usage ● Predictable and Consistent Workloads ○ I.e Available Engines = minimum number concurrent requests ● Always on and waiting for new job submissions (i.e. Automations, Flow Workspace Apps, etc.) ● Stream Processing* See FME Flow Administration: Planning and Performing an FME Flow Installation for more information CPU-Usage (Dynamic) ● Unpredictable Workloads. Includes but not limited to: ○ Automations and Workspace Apps ○ Reducing volume in job queues ○ Infrequent but intensive jobs ○ Irregular but critical jobs ○ Stream processing* FME Engine Types
- 36. Remote Engine Service Standard and/or CPU-Usage Engines deployed close to your data. Available outside your network on accessible endpoints or in the Cloud. FME Engine Types
- 37. Remote Engine Service Recommended Usage ● Operations in multiple networks (on-premise, on-cloud, hybrid/multi cloud) ● Easier Installation Process Distributed Engine ● Must be within the same network as the rest of the FME Flow Components ○ Bidirectional ports and continuous network traffic ● More considerations/planning required FME Engine Types
- 38. Engine Requirements ● 1 CPU Core per Engine ○ Applies to Standard AND CPU-Usage ● Memory (RAM) ○ Job dependent (review Job Logs) ■ Queues can help route resource heavy jobs to the appropriate engine ● Dependencies ○ ArcGIS, Python, Custom Transformers Distributed Engine FME Engine Types
- 39. “What are the basic hardware recommendations?”
- 40. Data ● Size and Volume ● Formats ● Location ● Future Growth Workflows ● Processes and Transformations ● Real-time or Batch ● Parallel or Sequential ● Frequency ● Performance
- 41. Hardware Recommendations Basic Better Best FME Flow Engine Count 2 4 8+
- 42. Hardware Recommendations Basic Better Best FME Flow Engine Count 2 4 8+ Processor (CPU) 4 6 10+
- 43. Hardware Recommendations Basic Better Best FME Flow Engine Count 2 4 8+ Processor (CPU) 4 6 10+ Memory (RAM) 8 GB 16 GB 32 GB
- 44. Hardware Recommendations Basic Better Best FME Flow Engine Count 2 4 8+ Processor (CPU) 4 6 10+ Memory (RAM) 8 GB 16 GB 32 GB Disk Space 100GB 150GB 200GB
- 45. “What considerations should you keep in mind with Esri when configuring FME Flow?”
- 46. FME Flow & Esri ArcGIS ● An ArcGIS Server license is required for most Esri formats (with exceptions) ● ArcGIS Server must be installed and licensed on the same machine as FME Flow ● Version compatible: ArcGIS must be compatible with FME.
- 47. “What resources do I need to set up SSL?”
- 49. ● Asymmetric encryption or public-key cryptography ○ Public Key/Certificate ○ Private Key HTTPS Configuration
- 50. ● Asymmetric encryption or public-key cryptography ○ Public Key/Certificate ○ Private Key ● Certificate formats ○ .CER/.CRT file ○ .PFX/.P12 file HTTPS Configuration
- 51. ● Asymmetric encryption or public-key cryptography ○ Public Key/Certificate ○ Private Key ● Certificate formats ○ .CER/.CRT file ○ .PFX/.P12 file ● Pre-requisites ○ Familiarity with CA instructions and certificate access ○ Familiarity with your web app’s SSL configuration/certificates HTTPS Configuration
- 52. ● Asymmetric encryption or public-key cryptography ○ Public Key/Certificate ○ Private Key ● Certificate formats ○ .CER/.CRT file ○ .PFX/.P12 file ● Pre-requisites ○ Familiarity with CA instructions and certificate access ○ Familiarity with your web app’s SSL configuration/certificates ● Optional configuration ○ Reverse proxy ○ Self signed certificates HTTPS Configuration
- 53. ● Asymmetric encryption or public-key cryptography ○ Public Key/Certificate ○ Private Key ● Certificate formats ○ .CER/.CRT file ○ .PFX/.P12 file ● Pre-requisites ○ Familiarity with CA instructions and certificate access ○ Familiarity with your web app’s SSL configuration/certificates ● Optional configuration ○ Reverse proxy ○ Self signed certificates ● HTTPS on Linux HTTPS Configuration
- 54. ● Asymmetric encryption or public-key cryptography ○ Public Key/Certificate ○ Private Key ● Certificate formats ○ .CER/.CRT file ○ .PFX/.P12 file ● Pre-requisites ○ Familiarity with CA instructions and certificate access ○ Familiarity with your web app’s SSL configuration/certificates ● Optional configuration ○ Reverse proxy ○ Self signed certificates ● HTTPS on Linux ● Upgrade requires re-configuration HTTPS Configuration
- 55. ● Asymmetric encryption or public-key cryptography ○ Public Key/Certificate ○ Private Key ● Certificate formats ○ .CER/.CRT file ○ .PFX/.P12 file ● Pre-requisites ○ Familiarity with CA instructions and certificate access ○ Familiarity with your web app’s SSL configuration/certificates ● Optional configuration ○ Reverse proxy ○ Self signed certificates ● HTTPS on Linux ● Upgrade requires re-configuration ● HTTPS when working with certain transformers HTTPS Configuration
- 56. ● Configuring for HTTPS ● Configuring FME Flow for HTTPS ● Use a Reverse Proxy with FME Server ● FME Flow Troubleshooting: Configuring for HTTPS/SSL Resources
- 57. “What User Authentication Types does FME support?”
- 58. System Users ● Default system users- admin, author, guest and user ● Default system roles- fmeadmin, fmesuperuser, fmeauthor, fmeguest and fmeuser
- 59. System Users ● Default system users- admin, author, guest and user ● Default system roles- fmeadmin, fmesuperuser, fmeauthor, fmeguest and fmeuser ● Role-Based Access Control vs User-based access control
- 60. System Users ● Default system users- admin, author, guest and user ● Default system roles- fmeadmin, fmesuperuser, fmeauthor, fmeguest and fmeuser ● Role-Based Access Control vs User-based access control ● Role templates
- 61. System Users ● Default system users- admin, author, guest and user ● Default system roles- fmeadmin, fmesuperuser, fmeauthor, fmeguest and fmeuser ● Role-Based Access Control vs User-based access control ● Role templates ● Permissions- General vs specific
- 62. System Users ● Default system users- admin, author, guest and user ● Default system roles- fmeadmin, fmesuperuser, fmeauthor, fmeguest and fmeuser ● Role-Based Access Control vs User-based access control ● Role templates ● Permissions- General vs specific ● Password policy enforcement
- 63. System Users ● Default system users- admin, author, guest and user ● Default system roles- fmeadmin, fmesuperuser, fmeauthor, fmeguest and fmeuser ● Role-Based Access Control vs User-based access control ● Role templates ● Permissions- General vs specific ● Password policy enforcement ● Password reset
- 64. System Users ● Default system users- admin, author, guest and user ● Default system roles- fmeadmin, fmesuperuser, fmeauthor, fmeguest and fmeuser ● Role-Based Access Control vs User-based access control ● Role templates ● Permissions- General vs specific ● Password policy enforcement ● Password reset ● MFA feature limitation
- 66. LDAP/Active Directory Users ● Protocol ○ LDAP ○ LDAPS
- 67. LDAP/Active Directory Users ● Protocol ○ LDAP ○ LDAPS ● Pre-requisites ○ Standalone Domain Controller ○ Port, Connection Encryption, Authentication type ○ Search /Service account
- 68. LDAP/Active Directory Users ● Protocol ○ LDAP ○ LDAPS ● Pre-requisites ○ Standalone Domain Controller ○ Port, Connection Encryption, Authentication type ○ Search /Service account ● Import Users/groups
- 69. LDAP/Active Directory Users ● Protocol ○ LDAP ○ LDAPS ● Pre-requisites ○ Standalone Domain Controller ○ Port, Connection Encryption, Authentication type ○ Search /Service account ● Import Users/groups ● Optional ○ Connection fields
- 70. LDAP/Active Directory Users ● Protocol ○ LDAP ○ LDAPS ● Pre-requisites ○ Standalone Domain Controller ○ Port, Connection Encryption, Authentication type ○ Search /Service account ● Import Users/groups ● Optional ○ Connection fields ● Synchronizing
- 71. LDAP/Active Directory Users ● Protocol ○ LDAP ○ LDAPS ● Pre-requisites ○ Standalone Domain Controller ○ Port, Connection Encryption, Authentication type ○ Search /Service account ● Import Users/groups ● Optional ○ Connection fields ● Synchronizing ● SSO/Kerberos
- 72. Azure Microsoft Entra ID Users ● Protocol- OAuth 2.0 / OpenID Connect
- 73. Azure Microsoft Entra Users ● Protocol- OAuth 2.0 / OpenID Connect ● Pre-requisites ○ HTTPS configuration
- 74. Azure Microsoft Entra Users ● Protocol- OAuth 2.0 / OpenID Connect ● Pre-requisites ○ HTTPS configuration ● Import Users/groups
- 75. Azure Microsoft Entra Users ● Protocol- OAuth 2.0 / OpenID Connect ● Pre-requisites ○ HTTPS configuration ● Import Users/groups ● Optional configuration ○ Reverse proxy/LB ○ Secondary Tenant Access
- 76. SAML Users ● Protocol- SAML 2.0
- 77. SAML Users ● Protocol- SAML 2.0 ● Pre-requisites ○ HTTPS configuration
- 78. SAML Users ● Protocol- SAML 2.0 ● Pre-requisites ○ HTTPS configuration ● Automatic User Import on first login
- 79. SAML Users ● Protocol- SAML 2.0 ● Pre-requisites ○ HTTPS configuration ● Automatic User Import on first login ● Optional configuration ○ Reverse proxy/LB ○ Attribute field Mapping ○ Signed Requests ○ Advanced Settings under Application.properties file
- 80. Resources ● User Management ● Security- Password features ● Authentication Services ● Configuring FME Flow for SAML Authentication ● Create an FME Flow Azure Active Directory Web Connection in FME Form ● FME Flow Troubleshooting: Users/Roles ● FME Flow Troubleshooting: Windows Active Directory ● FME Flow Troubleshooting: Integrated Windows Authentication or Single Sign On ● FME Flow Troubleshooting: Azure Active Directory ● FME Flow Troubleshooting: SAML
- 81. “What kind of maintenance and expertise is required?”
- 82. 1 2 3 Installation ● Document everything ○ Networking ○ Architecture ○ Service Accounts ● Version compatibility Upgrades ● Review ○ Documentation ○ Changelog ○ Compatibilities ● Test before Prod ● Backup Maintenance ● Regular backups ● Monitor ● Cleanup tasks ● Stay informed ○ community.safe.com ○ safe.com
- 83. 8 Resources
- 84. Get our Ebook Spatial Data for the Enterprise fme.ly/gzc Guided learning experiences at your fingertips academy.safe.com FME Academy Resources Check out how-to’s & demos in the knowledge base support.safe.com Knowledge Base Webinars Upcoming & on-demand webinars safe.com/webinars
- 85. Peak of Data Integration 2025 - Call for Presentations Now Open ● Abstracts due Nov 29th, 2024 ● All levels FME proficiency welcome ● 15 & 25 min options (incl. Q&A) ● Special speaker rate for accepted talks ● Registration is open! peakofdataintegration.com/call-for-presentations
- 86. 9 Next Steps
- 87. Register Now Tune into Part 2!.
- 88. We’d love to help you get started. Get in touch with us at [email protected] Experience the FME Accelerator Contact Us A world where data is not just a commodity but a catalyst for real change. fme.safe.com/accelerator Next Steps
- 89. ClaimYour Community Badge & Dive into the new Community! ● Get community badges for watching webinars ● community.safe.com ● Today’s code: R2HBX5 Join the Community today! Next Steps
- 90. 10 Q&A
- 91. ThankYou Recap of Next Steps 1 Follow us on LinkedIn! 2 Contact us 3 Experience the FME Accelerator Please fill out our webinar survey