Skip to main content
Solved

FME Server and running workspaces in sequence

  • July 3, 2023
  • 1 reply
  • 76 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.

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

1 reply

david_r
Celebrity
  • 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.


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