The dynamic engines capability is a very good extension of the FME Server capabilities. At this moment, it is possible to assign repositories to a dynamic engine. However, I think it would be interesting to be able to assign specific workspaces to a dynamic engine. I that case it is possible to only use specific workspaces with this functionality without the need to put these in a separate repository. It would be even more interesting to be able to separate bought credits for dynamic engines so we can assign different budgets for different workspaces.
Archived
Assign specific workspaces to dynamic engine
Hi g_karssenberg,
Whilst it's not currently possible to add individual Workspaces to a Job Queue from the Engines page I just thought I'd mention that depending on how you are setting the Job up to run their may still be the option to set it for the workspace, without doing it for the whole Repository.
If you are submitting the workspace through the Run Workspace page, a Schedule, or an Automation, there is an option to assign a Job Queue under the 'Advanced' section.
Login to the community
No account yet? Create an account
An FME Account is required to contribute
LoginEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.