Hi Goochy,

 

The fmeInstance parameter in FME Server 2012 is what we call a  TM Parameter or Transformation Parameter so a parameter used by the FME Server core rather than an FME parameter (a parameter of a workspace). So it won't work to set it as an FME parameter.  And I'm afraid it was not possible to set TM parameters in the FMEServerJobSubmitter in FME 2012 although it is in FME Server 2013.

 

There is a a workaround:

 

Get the URL to run the Job from the WebUI using the configure page of the workspace

 

Use the HTTPFetcher in the first workspace to fetch this URL and include the tm parameter like this:

 

http://host/fmejobsubmitter/Samples/austinApartments.fmw?opt_servicemode=sync&tm_fmeInstance=Engine1&...all your FME parameters

 

 

Not sure if this helps you but in FME Server 2013 we have a much simpler approach to Job Routing.

 

 

---

G'day,

Finally got around to trying the HTTPFetcher out, and yes it worked but I had to add credentials that I don't want public, and another workbench I needed this to work with, has a loop that generates a possible table to use, so I need the FMEServerJobSubmitter to work to tell me if the called workbench was successful or not.

 

 

Might have to take the plunge and try 2013 out.

---