It would be very helpful if you had an option for a concatenation of workspaces in the scheduler of the FME server.
At the moment, I use an additional FME process (with various FMEServerJobsubmitters) to concatenate the workspaces.
I would prefer it, if you could set this chaining in the admin interface of the FME server for the scheduled jobs.
This would not require an additional management process in the future.
In my case, I can not set up several scheduled jobs because they have a temporal dependency. For example, the following process may be started after the previous one completes successfully.
Chaining of workspaces in the scheduler of the FME server
FME Flow
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
You can already accomplish the same thing using notififcations and the workspace subscriber:
https://docs.safe.com/fme/2016.1/html/FME_Server_Documentation/Content/ReferenceManual/Workspace-Subscriber.htm
Another way is engine tagging:
https://docs.safe.com/fme/html/FME_Server_Documentation/Content/AdminGuide/Configure_Job_Routing.htm
Name (tag) an engine and give that name (tag) in Advanced Settings/Job Routing Tag in the schedule.
I have an overnight schedule of 4 workspaces, they run for a couple of hours each. I schedued them half an hour after each other and routed to the same engine so the workspaces patiently queue up and wait their turn to be processed by the engine one by one :)
Edit:
I forgot to mention to set the Job Priority as well. It should be sequential (or at least increasing) in the job run order and lower than than the other schedules.
- enable scheduled workspaces/jobs to be dependent on each other (by success/failure)
- redesign scheduler UI to support visual chaining of schedules/jobs with (aka connections in Desktop)
- redesign scheduler UI to show past jobs with actual runtime
- redesign scheduler UI to show future jobs with expected runtime (and dependencies)
In my opinion it is too much hassle if you have to set up notifications and subscriptions for this kind of simple (?) task ...I think this idea is in the pipeline for FME Server 2018.
Have a look at the end of this presentation:
https://www.safe.com/presentations/new-horizons-for-workbench-viewing-and-editing-in-the-browser
So there are lots of different ways that job dependency / chaining can be accomplished:
For my workflows they all seem kludgy. I really think this functionality belongs with the definition of a schedule. We have a LOT of scheduled jobs and the number is only going to grow. Its important that I am able to see what is dependent on what easily. None of the above solutions can do that. They would all require me to run some kind of automated process interrogating all my schedules to find out about dependency trees.
While this may not tick all the boxes of the initial request and subsequent comments, currently available in the latest beta of FME Server 2018.0 is an exciting new feature called Automations! This has the opportunity to revolutionize the way we have configured Notifications (Publications, Subscription, Topics) and Scheduling in FME Server!
Featuring a simple drag-and-drop interface, you can create notification workflows and chain events together. I encourage everyone to check this out!
Note: As this is a beta feature, please understand that functionality and appearance is subject to change as the product evolves.
@wicki @esko @guy_lafleur – Let us know if we are on the right track to address your idea and comments, or how Automations can be improved to more closely match it!Rylan, yes you are on the right track. Everything that makes it easier to "program" FME Server is great for all of us who spend most our working hours in other duties than fiddling with FME.
Along those lines, I would also like to see some improvement in the Scheduler GUI (as I suggested earlier here:
https://knowledge.safe.com/idea/32771/improve-fme-server-schedules-dashboard-layout.html
).
Along those lines, I would also like to see some improvement in the Scheduler GUI (as I suggested earlier here:
https://knowledge.safe.com/idea/32771/improve-fme-server-schedules-dashboard-layout.html
).This idea will be marked as In Beta – we plan to release FME Server Automations in 2019.0! Please check out the latest betas.
Note: Screenshot taken from FME Server 2019.0 beta Build 19224.
---
Please note that this feature is currently included with the beta version of FME Server and its functionality and appearance are subject to change as the product continues to evolve before the official release.
Should this feature or its implementation not address your concerns, related to this Idea posting, please let us know by leaving a comment.
As with all beta features and beta versions of our software, they are not considered production-safe and should be incorporated into your workflows with consideration and testing.
Note: FME Server 2019.0 was released on April 2 2019. This idea status marked as Released.