I have attempted to configure Job Routing in FME Server 2017 in the config file but it is not working?
Solved
How do I configure Job Routing in FME Server 2017?
+21- Safer
Best answer by steveatsafe
New in FME Server 2017, Job Routing is no longer configured in the config files (fmeServerConfig.txt).
We have changed the terminology that refers to Job Routing, and it is now called Job Queues in the Web UI and Documentation. (not to be confused with the "Queued Jobs" found in the Jobs page).
We felt this change describes better the purpose of the functionality. Think of a purchasing tickets at a baseball stadium and its ticket agents representing the queues.
If you are using FME Server 2017.0 you'll need to use the REST API to configure the Job Routing. However, starting 2017.1 you'll be able to use the Web UI.
One slight subtlety is that the REST API still refers to Job Routing terminology. This is for backwards compatibility.
See the documentation for more information (click here)
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.
+2Did you follow these instructions?
To configure job routing, use the FME Server REST API V3. Job routing is configured using
/transformations/jobroutes/
+13- Safer
- Best Answer
New in FME Server 2017, Job Routing is no longer configured in the config files (fmeServerConfig.txt).
We have changed the terminology that refers to Job Routing, and it is now called Job Queues in the Web UI and Documentation. (not to be confused with the "Queued Jobs" found in the Jobs page).
We felt this change describes better the purpose of the functionality. Think of a purchasing tickets at a baseball stadium and its ticket agents representing the queues.
If you are using FME Server 2017.0 you'll need to use the REST API to configure the Job Routing. However, starting 2017.1 you'll be able to use the Web UI.
One slight subtlety is that the REST API still refers to Job Routing terminology. This is for backwards compatibility.
See the documentation for more information (click here)
+6- Contributor
You can configure job routing in fmeServerconfig.txt in 2017.0 (we are still using it like this but with 2017.1 you need Web-UI, no longer in txt file)
#------------------ # Job Routing #-------------------------------------------- TM_QUEUE_TYPE=DEFAULT TM_DEFAULT_TAG=default
TM_ENGINE_1=GISFME01_Engine1:fast mapbase default TM_ENGINE_2=GISFME01_Engine2:normal asset default TM_ENGINE_3=GISFME01_Engine3:batch image default
2017.1.x - see below
