Skip to main content
Solved

fme job submitter - run multiple times in workspace

  • May 22, 2018
  • 5 replies
  • 93 views

oliver.morris
Contributor
Forum|alt.badge.img+14

Hi,

I am trying to run this workspace on fme cloud, it has many engines, why isnt it running against 3 engines in parallel, this seems to be the same whether I run it from desktop or from the cloud directly..

Many Thanks

Oliver

Best answer by redgeographics

If the jobs need to be submitted in sequence then it's probably best to connect them in sequence. So that first all jobs from FMEServerJobSubmitter 1 are run, then 2, then 3. You can use the feature coming out of the summary port to trigger the next SQLExecutor which then in turn triggers the next FMEServerJobSubmitter.

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.

5 replies

austinh
Contributor
Forum|alt.badge.img+4
  • Contributor
  • May 22, 2018

In the FMEServerJobSubmitter XFMR, did you set the Submit Job to "In Parallel?


oliver.morris
Contributor
Forum|alt.badge.img+14
  • Author
  • Contributor
  • May 23, 2018

In the FMEServerJobSubmitter XFMR, did you set the Submit Job to "In Parallel?

Unfortunately each individual jobsubmitter needs to run in sequence and wait for the job to complete. I would just like to run a single job which then goes off an runs three separate job submitters fully utilising all the engines I have.

 

 


redgeographics
Celebrity
Forum|alt.badge.img+62
  • Celebrity
  • Best Answer
  • May 23, 2018

If the jobs need to be submitted in sequence then it's probably best to connect them in sequence. So that first all jobs from FMEServerJobSubmitter 1 are run, then 2, then 3. You can use the feature coming out of the summary port to trigger the next SQLExecutor which then in turn triggers the next FMEServerJobSubmitter.


oliver.morris
Contributor
Forum|alt.badge.img+14
  • Author
  • Contributor
  • May 23, 2018

If the jobs need to be submitted in sequence then it's probably best to connect them in sequence. So that first all jobs from FMEServerJobSubmitter 1 are run, then 2, then 3. You can use the feature coming out of the summary port to trigger the next SQLExecutor which then in turn triggers the next FMEServerJobSubmitter.

Hi, Sorry I should have been clearer, after the first executor I would like them to run at the same time across three different engines. Like so:

 

 

at the moment, it appears to only run through the first then, the second branch then finally the third. Is there a better way or do I need to create 3 separate workspaces and run them all at once?

 

 

Many Thanks for the help.

takashi
Celebrity
  • May 23, 2018
Hi, Sorry I should have been clearer, after the first executor I would like them to run at the same time across three different engines. Like so:

 

 

at the moment, it appears to only run through the first then, the second branch then finally the third. Is there a better way or do I need to create 3 separate workspaces and run them all at once?

 

 

Many Thanks for the help.
Yes, a possible way is to create three worksapaces corresponding to each branch in the current workspace and submit jobs to run them from three FMEServerJobSubmitters (Submit Jobs: In Parallel) in another workspace.