How to choose ETL configuration options
This page helps you pick the right input, output and connection setup for map.apps ETL.
Choose an input method
| Input | Use when |
|---|---|
|
Users provide local files. |
|
Users define an area of interest on the map. |
|
Users select existing map features and submit them to FME. |
|
Users start processing from search/result views. |
|
Users start from one selected search result feature. |
Choose an output method
| Output | Use when |
|---|---|
|
The workspace returns vector features that should be displayed on the map. |
|
The workspace produces downloadable files. |
|
The workspace runs asynchronously and users consume status or notifications. |
Choose connection and security setup
| Option | Recommended use |
|---|---|
ETL proxy servlet |
Default and most flexible option for protected environments and advanced integration. |
map.apps proxy |
Simple scenarios, usually without advanced security requirements. |
security.manager EE generic URL protection |
Legacy compatibility only. |
Quick recommendations
-
If users upload files and expect map output, start with
upload+map. -
If users need a clipped export, use
extent+download. -
If users process selected features, use
mapfeatures+statusordownload. -
If your process uses user context, enable
provideMapappsUserand optionallyprovideMapappsEmail.