Skip to main content

Hi!

I want to feed a series of workspaces into WorkSpaceRunner to be run in consecutive order. Most important is that the first one runs successfully to completion before the next one starts. Else the process should stop.

They are all part of a weekly update routine, but I want to keep each workspace separate, in order to be able to run them separately at other times.

I am not able to figure out how to use WorkspaceRunner for this, despite careful perusal of this forum. The part I do not understand is how to hold workspace 2 until nr 1 gives a go signal.

Thanks, Mats.E

Have you tried setting "Wait for job to complete" to Yes?

 

You will proably also want to read through the WorkspaceRunner documentation, there are several useful tips there:

http://docs.safe.com/fme/2018.1/html/FME_Desktop_Documentation/FME_Transformers/Transformers/workspacerunner.htm


Have you tried setting "Wait for job to complete" to Yes?

 

You will proably also want to read through the WorkspaceRunner documentation, there are several useful tips there:

http://docs.safe.com/fme/2018.1/html/FME_Desktop_Documentation/FME_Transformers/Transformers/workspacerunner.htm

This, and use a different WorkspaceRunner for each Workspace.

Master:

Slave a:

01_master.fmwt


Sorry, I was unclear. First, having to run a series of runners kind of defy the purpose, I think.

So I read the current list of workspaces from a folder and feed them to the runner like this.

The documentation speaks only of the workspace in singular, and the WorkSpaceRunner only allows input of one workspace, so I came up with the list idea above. And I have of course set the switch to wait for the job to complete. But which job? Will it stop on the first unsuccessful one, or will it simply report a failure and go on with the next? I am reluctant to make it fail on purpose.

Going over the above, I now realised a mistake. I used path_filename instead of path_windows for the parameter to pass on to the runner. This caused all workspaces to fail.

Running the above set up seems to work now. Yipee!

It's a pity though that I get no feedback from each process, neither during the run nor afterwards, other than that it went well.

/Mats.E

 


Reply