Could someone in the community provide an explanation of where FME ETL development occurs?
Is it in FME Workbench; or, FME Server?
Question
Authoring FME ETLs
I working within my organization to help fellow team members understand the differences between FME Workbench and FME Server.
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+21- Safer
Hi,
Most of the information you seek is found here:
http://cdn.safe.com/training/tutorials/FME-Server-Tutorial.pdf
and
http://docs.safe.com/fme/html/FME_Workbench/Default.htm#About_FME_Server.htm
Basically the development takes place in workbench FME server is more about how to initiate the transformation and how to serve the results.
Hope this helps,
Itay
Hi,
Itay has given some good starting points below.
In very broad terms, it works like this:
FME Desktop is an authoring tool. It will allow you to create workspaces that you can run within FME Desktop.
The workspaces you authored with FME Desktop may also be published on FME Server. The workspaces will then be available in a more distributed fashion. The workspaces can then be run using either the web-based GUI of FME Server, or via the FME Server REST API.
In both instances, the actual workspace is run using the exact same engine, so the results are the same. It is the way you run the workspace that differs.
Hope this clarifies it somewhat.
David