Skip to main content
Solved

What is a controller in therms of workbench? Is that only a term?


Forum|alt.badge.img

Hi

I am new to FME. Coming from ESRI background and FME terminology is new to me.

I have 30 or so workbenches - some of them are called something_controller and other of them are called something_runer

They see to be just regular WBs - doing some stuff to data. I don't see any relationship between a controller WB and a runner WB, e.g. controller calling the runner in any way. Being new I am not sure if this is at all possible.

So do the naming suggest any relationship between WBs or this is just a term in the naming?

Thanks

Best answer by davideagle

Have a look inside the "controller" workspaces and see if you can see a Transformer called the WorkspaceRunner. If you can, open up the parameters and check to see which "runner" workspace it is calling.

This approach is commonly used to perform batch processing. where the controller tells the runner which files to process and the runner does the work, often a file or a geography at a time and sometimes concurrently up to a maximum of 7 processes.

View original
Did this help you find an answer to your question?
This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, 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.

5 replies

davideagle
Contributor
Forum|alt.badge.img+21
  • Contributor
  • Best Answer
  • January 29, 2016

Have a look inside the "controller" workspaces and see if you can see a Transformer called the WorkspaceRunner. If you can, open up the parameters and check to see which "runner" workspace it is calling.

This approach is commonly used to perform batch processing. where the controller tells the runner which files to process and the runner does the work, often a file or a geography at a time and sometimes concurrently up to a maximum of 7 processes.


Forum|alt.badge.img
  • Author
  • January 29, 2016
davideagle wrote:

Have a look inside the "controller" workspaces and see if you can see a Transformer called the WorkspaceRunner. If you can, open up the parameters and check to see which "runner" workspace it is calling.

This approach is commonly used to perform batch processing. where the controller tells the runner which files to process and the runner does the work, often a file or a geography at a time and sometimes concurrently up to a maximum of 7 processes.

Hi,

thanks. No it doesn't have this transformer, but it has FMEServerJobSubmitter, at least one of those.

It points to another workspace (fmw).

Is this the same as what you said about the batch processing?


davideagle
Contributor
Forum|alt.badge.img+21
  • Contributor
  • January 29, 2016
garnet wrote:

Hi,

thanks. No it doesn't have this transformer, but it has FMEServerJobSubmitter, at least one of those.

It points to another workspace (fmw).

Is this the same as what you said about the batch processing?

Absolutely, though in this case the scenario is subtly different. It is looking to call another process hosted on FME Server. So in this case it's likely that the Controller workspace is also hosted on FME Server too and it is triggered and then runs the sub processes. It sounds like you'll have FME Server installed somewhere and these processes are a backup of what is installed on FME Server.

The FMEServerJobSubmitter is the WorkspaceRunners big brother!


Forum|alt.badge.img
  • Author
  • February 1, 2016

Thanks

yes we have FME server and this is the WB just in Subversion. Normally everything is run on the server.


davideagle
Contributor
Forum|alt.badge.img+21
  • Contributor
  • February 1, 2016
garnet wrote:

Thanks

yes we have FME server and this is the WB just in Subversion. Normally everything is run on the server.

no worries


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