Skip to main content
Best Answer

Shutdown Python Script VS. WorkspaceRunner Transformer

  • March 13, 2019
  • 4 replies
  • 52 views
R
Forum|alt.badge.img

Hello again.

I was planning on setting up a sequence of translations to run where each successive translation is run by a WorkspaceRunner transformer in the previous.

The problem with this is that placing a WorkspaceRunner at the end of a translation makes it dependent on the translation succeeding, and my chain of many translations could be jeopardized by something out of my control, such as a "403 Forbidden" error in an HTTPCaller.

My questions are:

A) Can I run a .bat file as a Shutdown Python Script without the translation where that script resides remaining running? In other words, is there a Python version of "Wait for Job to Complete: No" ?

B) If not, is there a way to place the WorkspaceRunner so that it both

  1. Doesn't start the next translation in the sequence until most or all of the operations are complete, and
  2. Isn't dependent on any other transformers succeeding

The reason these requirements are in place is so that more than one translation isn't running at a time, and so that I can rule out widespread failure due to errors listed above.

Thanks. Your help and ideas are always appreciated.

Best answer by jdh

Have you considered one master controller workspace, with multiple workspace runners in sequence, instead of chaining them together in each individual workspace?

You would would have more control over what to do if a child workspace fails.

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.

4 replies

jdh
Contributor
Forum|alt.badge.img+40
  • jdhContributor
  • Contributor
  • Best Answer
  • March 13, 2019

Have you considered one master controller workspace, with multiple workspace runners in sequence, instead of chaining them together in each individual workspace?

You would would have more control over what to do if a child workspace fails.

R
Forum|alt.badge.img

Have you considered one master controller workspace, with multiple workspace runners in sequence, instead of chaining them together in each individual workspace?

You would would have more control over what to do if a child workspace fails.

I hadn't considered it yet. I would need some sort of feedback of translation completion (success or failure) as input in order for it to work. Would that be possible?

jdh
Contributor
Forum|alt.badge.img+40
  • jdhContributor
  • Contributor
  • March 13, 2019

I hadn't considered it yet. I would need some sort of feedback of translation completion (success or failure) as input in order for it to work. Would that be possible?

If you set wait for workspace to complete to "yes", then the success and failure ports will only release the corresponding feature once the workspace is completed.

R
Forum|alt.badge.img

If you set wait for workspace to complete to "yes", then the success and failure ports will only release the corresponding feature once the workspace is completed.

Thank you so much again. Using the type of control translation you described will serve a couple of different purposes for us. Appreciate it!

Community Stats

32,182
Posts
122,173
Replies
39,855
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
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.