Skip to main content
  • EN
We have more than one FME Engine installed on our FME Server host. The Engines have different Versions, e.g. one Engine is 2012 and one 2013. This is inevitable in order to keep older workbenches functioning due to a lacking downward compatibility.

 

 

So far with FME 2012 Server I was able to define on which of the engines a service will be run by assigning a parameter such as 'tm_fmeInstance Engine1' on the FME Server Console command (line).

 

 

With FME 2013 Server this does no loger work. How am I to control the engine on which a service will be executed?
Found a possible answer to the above issue myself:

 

http://fmepedia.safe.com/articles/How_To/Assigning-jobs-to-a-subset-of-available-FME-Engines

 

 

We obviously neet to do some configuration work on our upgraded FME Server...
And here an even more direct way:

 

http://fmepedia.safe.com/articles/How_To/Assigning-jobs-to-specific-FME-Engines

 

 

Well, the two answers above and the given links are valid for SME 2012 Server only. The solution for FME 2013 Server is still needed.

Does this help?

http://docs.safe.com/fme/2013/html/FME_Server_AdminGuide/Content/AdminGuide/High_Avail_Install/Configure_Job_Routing.htm

 

Diagram showing Server Engines Tagged

Reply


Community Stats

30,147
Posts
114,431
Replies
37,790
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.