Skip to main content
Solved

FME Server 2019 - Does FME Server allow all workspaces in a Repository to be run as an individual scheduled task?


gfaulkner
Participant
Forum|alt.badge.img

I am wanting to publish around 60 workbenches to FME Server 2019 to run sequentially as a single scheduled task, however cannot find any configuration in the interface which would allow me to do this.

Ideally, I would want to be able to select the repository I publish the workbenches to and configure to run on one of our two engines of FME Server. This would save a lot of configuration time instead of having to create a unique schedule for every workbench.

Can anyone suggest a solution or advise if this is possible? (Maybe an idea for a future release of server?)

Thanks

Best answer by nielsgerrits

I do this using a FMEServerJobSubmitter or with a HttpCaller to the API. Schedule the single workspace that submits the children. Does that work for you?

View original
Did this help you find an answer to your question?

4 replies

nielsgerrits
VIP
Forum|alt.badge.img+54
  • Best Answer
  • November 1, 2019

I do this using a FMEServerJobSubmitter or with a HttpCaller to the API. Schedule the single workspace that submits the children. Does that work for you?


redgeographics
Celebrity
Forum|alt.badge.img+50

In addition to what @nielsgerrits has already suggested you could also chain them together in one big automation and run that on a schedule.


Forum|alt.badge.img+2

Hi @gfaulkner,

I agree with nielsgerrits the easiest way to do this since you have so many workspaces to schedule would be to create a parent workspace to submit all of these. I'd take a look at the FME Server Rest API and first I'd make a call to list all the workspaces in that repository:

https://docs.safe.com/fme/html/FME_REST/apidoc/v3/index.html#!/repositories/items_get_5

Then you can flatten the response JSON to retrieve the workspace name as an attribute which can be used in a second HTTPCaller in the Request URL to submit the jobs, rather than this being something you have to set manually for each one.

https://docs.safe.com/fme/html/FME_REST/apidoc/v3/index.html#!/transformations/submit_post_29

There is also an existing idea requesting a Schedule for Repositories so please consider adding a vote and any supporting comments here: https://knowledge.safe.com/content/idea/77546/scheduling-a-repository-to-run-workspaces-as-a-bat.html


gfaulkner
Participant
Forum|alt.badge.img
  • Author
  • Participant
  • November 11, 2019
hollyatsafe wrote:

Hi @gfaulkner,

I agree with nielsgerrits the easiest way to do this since you have so many workspaces to schedule would be to create a parent workspace to submit all of these. I'd take a look at the FME Server Rest API and first I'd make a call to list all the workspaces in that repository:

https://docs.safe.com/fme/html/FME_REST/apidoc/v3/index.html#!/repositories/items_get_5

Then you can flatten the response JSON to retrieve the workspace name as an attribute which can be used in a second HTTPCaller in the Request URL to submit the jobs, rather than this being something you have to set manually for each one.

https://docs.safe.com/fme/html/FME_REST/apidoc/v3/index.html#!/transformations/submit_post_29

There is also an existing idea requesting a Schedule for Repositories so please consider adding a vote and any supporting comments here: https://knowledge.safe.com/content/idea/77546/scheduling-a-repository-to-run-workspaces-as-a-bat.html

@hollyatsafe @nielsgerrits @redgeographics

Hi All. thanks for your responses. I'll up vote the existing idea. We ended up using 4 parent workspaces with FMEServerJobSubmitter's to meet our needs.

Thanks again, Grant


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings