The document outlines the integration of efficient and reusable FME components in web applications, emphasizing the functionality of FME server apps such as clean design, data streaming, and job submission. It discusses the benefits of creating generic components to streamline development while addressing common application requirements like file handling and parameter management. The presentation includes a demo showcasing file upload, content analysis, and data editing processes.

1. How to integrate efficient and
reusable FME components in
web applications

2. FME
User
Conference
20
22
Dennis Wilhelm
Consultant
con terra GmbH

3. 20
22
FME
User
Conference
FME Server Apps
Let’s start with

4. 20
22
FME
User
Conference

5. 20
22
FME
User
Conference
Functionality Overview
• Clean and easy to use websites / apps
• Published Parameters
• Data Streaming, Data Download, Job Submitter
• Custom design
• Optional authentication
• Galleries

6. 20
22
FME
User
Conference
• Hide complex information
• Because no user wants to see this
Why do we need that?

7. 20
22
FME
User
Conference
FME can do so much more
• Integrate FME into an existing
application
• Provide input data directly from
this app
• Use results directly where it
needs to be
• Create multi-step workflows
• Upload
• Edit
• Download

8. 20
22
FME
User
Conference
Integration Example
• Use FME in existing applications
• Data portals
• Intranet websites

9. 20
22
FME
User
Conference
Reusable Components
Implement

10. 20
22
FME
User
Conference
What does this mean?
• Most FME based apps need a similar set of
functionality
• Generic approaches saves time in the long run

11. 20
22
FME
User
Conference
Generic components
• Components are based on the REST interface
• Automatically changes if Workspaces or
other FME Server contents change
• Reduce coding

12. 20
22
FME
User
Conference
What do we usually need?
• UI Elements
• File Upload
• Parameter dialog
• File browsing
• App specifics
• e.g. selecting existing data, display
process result
• Backend
• Request handling
• SSO

13. 20
22
FME
User
Conference
Build generic components
• Automatically create UI elements from Workspace
information

14. 20
22
FME
User
Conference
Parameter REST Example

15. 20
22
FME
User
Conference
Parameters
• Mapping for most
important
parameter types

16. 20
22
FME
User
Conference
Upload widgets
• Validations
• File type / extensions
• File size

17. 20
22
FME
User
Conference
File validation before processing
• Test data before long running processes
• Are all requirements met?
• Geometry type
• CRS
• Which contents should be used
• ZIP-File contents
• FGDB Feature Classes

18. 20
22
FME
User
Conference
File handling
• List the contents of the
shared resources
• Filter files (e.g. FGDB contents)

19. 20
22
FME
User
Conference
The boring stuff…

20. 20
22
FME
User
Conference
Backend Service
• Use existing authentication methods
of existing app
• Backend service is required to handle
FME requests
App Backend
FME
Server

21. 20
22
FME
User
Conference
Handle timeouts
• Data streaming services are often used as API endpoints
• Many network infrastructures have timeouts
• Use asynchronous job submitter
• Write data to the data download directory manually with a UUID
$(FME_SHAREDRESOURCE_SYSTEM)/temp/engineresults/$(uuid).json
=>
https://<fme server>/fmedatadownload/results/$(uuid).json

22. 20
22
FME
User
Conference
Demo

23. 20
22
FME
User
Conference
Demo
• Upload file
• Analyze contents
• Which Feature Classes are available in a FGDB
• Validate CRS
• Available Attributes
• Convert to JSON
• Edit in map
• Download edited data with format conversion

24. 20
22
FME
User
Conference

25. Thank You!
d.wilhelm@conterra.de