Skip to main content
  • EN

In FME Server 2017 you can route a job to a specified engine by specifying the tag for that engine in the Job Routing Tag box in the Advanced panel of the Run Workspace dialog. However, I am calling the workspace from a workspace runner using the FMEServerJobSubmitter tool.

There is no facility in the workspace runner to enter the job routing tag. Also, when I publish the workspace runner to FME Server, there is no place to put in the job routing tag. I tried setting the FME_SERVER_REQUEST_PARAMETERS parameter to "tm_tag=my_engine_tag1" but it still failed when I ran the workspace runner because the workspace did not route to that engine.

Is there a way to set the job routing tag either when you publish the workspace to FME Server or when you call the workspace from the FMEServerJobSubmitter?

There a way to tie a repository to a tag, maybe this is the way to go.

Another solution may be to use a REST call instead of a workspace runner to launch your workspace.

In the FMEServerJobSubmitter (FME 2017+), if you click the down arrow next to Advanced, there is a box where you can set the Job Routing Tag.

In the FMEServerJobSubmitter (FME 2017+), if you click the down arrow next to Advanced, there is a box where you can set the Job Routing Tag.

Yes, that works. Actually the Job Routing Tag box is in FME Desktop 2016 FMEServerJobSubmitter as well. I just didn't see it as it was in the second screen.

 

 

Yes, that works. Actually the Job Routing Tag box is in FME Desktop 2016 FMEServerJobSubmitter as well. I just didn't see it as it was in the second screen.

 

 

Perfect! I'm glad that helped!

 

 

Reply


Community Stats

30,549
Posts
115,827
Replies
38,213
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.