Hello FME-community,
I want to upload a workspace to FME Server and ensure this workspace always runs with a default priority of 50.
Is there a way to set the default priority when publishing the workspace to FME Server?
OR
Can you change the default priority of workspaces once they are published at FME Server?
I know you can assign a priority when launching a workspace by the FMEServerJobSubmitter transformer, but this is not my intention in this case.
You can set the priority of the scheduled job via the Web UI under advanced, is that what you mean?
If you have a published parameter called tm_priority that contains the desired priority, I believe this will be used at run-time. At least, that's what the docs appear to be trying to say (they could be clearer).
If you have a published parameter called tm_priority that contains the desired priority, I believe this will be used at run-time. At least, that's what the docs appear to be trying to say (they could be clearer).
Yes use tm_priority. As itay says, it has to be part of the http call. So you may need to create a public parameter called tm_priority (maybe alias type so you say high priority = 10, low =200). That parameter won't do anything in the workbench itself but when you run the process it will pass &tm;_priority=10 etc in the http call.
In your case if you always want to to be 50. Just create a choice parameter (as public). Call it tm_priority and set the choice and default value as 50. Its ugly how users always see it, but if you make it a private parameter, it won't pass correctly.
Unfortunately, no, you cannot set a default priority for a workspace. You will have to specify the priority each time the workspace is executed (web interface, scheduler, API, etc).
This is a great idea and I would encourage you to add an entry to our Ideas exchange so that others can contribute to it and vote it up!
https://knowledge.safe.com/content/idea/list.html
Yes use tm_priority. As itay says, it has to be part of the http call. So you may need to create a public parameter called tm_priority (maybe alias type so you say high priority = 10, low =200). That parameter won't do anything in the workbench itself but when you run the process it will pass &tm;_priority=10 etc in the http call.
In your case if you always want to to be 50. Just create a choice parameter (as public). Call it tm_priority and set the choice and default value as 50. Its ugly how users always see it, but if you make it a private parameter, it won't pass correctly.
Thank you very much for your reply.
If I make it private, it also works for me with FME Server 2016.
This is a great idea and I would encourage you to add an entry to our Ideas exchange so that others can contribute to it and vote it up!
Unfortunately, no, you cannot set a default priority for a workspace. You will have to specify the priority each time the workspace is executed (web interface, scheduler, API, etc).
Thank you for your answer. The workaround jonathan proposed worked fine for adding a default priority.
You can set the priority of the scheduled job via the Web UI under advanced, is that what you mean?
Thank you for answering. In this way I learned you can assign a priority to a scheduled job. I wanted to assign a priority to a job while uploading a workspace to FME Server. This is possible by creating a published or private parameter "tm_priority" as jonathan proposed.
Thank you for your answer. The workaround jonathan proposed worked fine for adding a default priority.
I only tested it in FME Server 2016, so I cannot confirm for FME Server 2015.
Yes use tm_priority. As itay says, it has to be part of the http call. So you may need to create a public parameter called tm_priority (maybe alias type so you say high priority = 10, low =200). That parameter won't do anything in the workbench itself but when you run the process it will pass &tm;_priority=10 etc in the http call.
In your case if you always want to to be 50. Just create a choice parameter (as public). Call it tm_priority and set the choice and default value as 50. Its ugly how users always see it, but if you make it a private parameter, it won't pass correctly.