Skip to main content
Solved

FME Server and running workspaces in sequence

  • July 3, 2023
  • 1 reply
  • 102 views
vxn43
Supporter
Forum|alt.badge.img+18

I have 3 workspaces; they need to be run like this:

​

1st to be run is workspaceA, 2nd to be run is workspaceB, 3rd to be run is

workspaceC.

​

I know in Scheduler I can set each to run for example:

​

workspaceA runs at 905p, workspaceB runs at at 910p, workspaceC runs at 915p.

​

But, this approach poses a risk that if workspaceA fails during its run, workspaceB and workspaceC will still run and that could corrupt my data. It seems more prudent that if, for example, workspaceA fails to run that workspacesB and C will not run.

​

What is the best way to deal with this situation using FME Server?

​

Should I create a new workspace using FMEJobSubmitter Transformer or add FMEJobSubmitter Transformer to the workspaceA, B, and C?

​

​

Best answer by david_r

My recommendation is to use Automations for this, it's very easy to chain workspaces that way, and even introduce controlled error handling if a problem occurs. You can even pass information between workspaces using the Automation writer.

Alternatively, you can also use the FMEJobSubmitter transformer within a master workspace, but personally I find Automations even more intuitive and simpler to use.

    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.

    1 reply

    david_r
    Celebrity
    • david_rCelebrity
    • 8392 replies
    • Best Answer
    • July 3, 2023

    My recommendation is to use Automations for this, it's very easy to chain workspaces that way, and even introduce controlled error handling if a problem occurs. You can even pass information between workspaces using the Automation writer.

    Alternatively, you can also use the FMEJobSubmitter transformer within a master workspace, but personally I find Automations even more intuitive and simpler to use.

    Community Stats

    32,070
    Posts
    121,771
    Replies
    39,696
    Members

    Latest FME

    Terms & ConditionsCookie settingsAccessibility statement
    A product of
    Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.