Hello,
I'm not able to figure out how to run child jobs using FMEServerJobSubmitter based on a list.
What I have done is a "master" fme workspace which spawn "jobs" passing parameters to instances of another workspace. It's done based on list so there is a list - and if there are 10 elements in the list 10 jobs will be submitted to the server. It means 2 available engines will run the jobs and the rest will be queued. It's undesired situation, since this will run on a 6 engine FME server and the current solution will use all of the available engines. It's undesired because estimation of this job running on 1 engine is 10 days (it's large raster). So it would block all other jobs for quite amount of time - on 6 engines obviously it would take less time like 1-2 days, however it's still not acceptable.
So the question - is it possible to limit the FMEServerJobSubmitter to be running only in 2 instances at once, so looping the list - taking 2 (or N) elements, running job submitters for these elements waiting until the jobs finish and then taking another element from list.
Thanks for help
Tomasz