Skip to main content
  • EN

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?

​

​

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.

Reply


Community Stats

30,162
Posts
114,483
Replies
37,809
Members
Terms & ConditionsCookie settings
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.