We have a single instance of FME Server shared across multiple utilities (i.e, separate finances). We recently purchased an additional engine for one of our utilities, who has been consistently using the engine owned and paid for by another. Even though they now have their own, this utility's users continue to use the engine owned by the other utility, which hoses up that utility's jobs. Is there any way to limit engine access by user so that each utility's users can only see the engine specifically for them?
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
- 7842 replies
Hi @mgusman, I don't think you can assign an engine to a specific user directly. A possible workaround is to create a new queue and configure as:
- newly create repositories only for the user if necessary,
- publish all the workspaces for the user into the repositories,
- assign the repositories and the additional engine to the new queue,
- de-assign the repositories and the additional engine from all the existing queues.
With the configuration above, the additional engine will run only for the workspaces within the repositories specific to the user, and the existing engine won't run for them.
See here to learn more about Job Queues.
https://docs.safe.com/fme/html/FME_Server_Documentation/Content/WebUI/Job-Queues.htm#