Skip to main content
Solved

Run FME transformer after processing of a writer

  • December 18, 2017
  • 2 replies
  • 329 views

Forum|alt.badge.img

Hi,

In my workbench, I am writing a file which i want to send as attachment in an email notification from the same workbench. How can i control my FMEServerEmailGenerator to work if only the file is written?

Note: I am using Fanout process in writer.

Best answer by nielsgerrits

I know 2 ways to do this:

- WorkspaceRunner. Creator to start WorkSpaceRunner. First WorkSpaceRunner to process data. Second WorkSpaceRunner to mail attachment.

 

- FeatureWriter. Use Summary feature from FeatureWriter to initiate the next Transformer. I often use a Holder to prevent starting the Transformer after the FeatureWriter before all features are written.

I prefer the FeatureWriter because this way you can keep it in one Workspace.

The downside of using a FeatureWriter in server is that the field numFeaturesOutput in the job summary is not handled correctly. Using a classic writer this number tells the number of written features correctly.

View original
Did this help you find an answer to your question?

2 replies

nielsgerrits
VIP
Forum|alt.badge.img+54
  • Best Answer
  • December 18, 2017

I know 2 ways to do this:

- WorkspaceRunner. Creator to start WorkSpaceRunner. First WorkSpaceRunner to process data. Second WorkSpaceRunner to mail attachment.

 

- FeatureWriter. Use Summary feature from FeatureWriter to initiate the next Transformer. I often use a Holder to prevent starting the Transformer after the FeatureWriter before all features are written.

I prefer the FeatureWriter because this way you can keep it in one Workspace.

The downside of using a FeatureWriter in server is that the field numFeaturesOutput in the job summary is not handled correctly. Using a classic writer this number tells the number of written features correctly.


Forum|alt.badge.img
  • Author
  • December 18, 2017
nielsgerrits wrote:

I know 2 ways to do this:

- WorkspaceRunner. Creator to start WorkSpaceRunner. First WorkSpaceRunner to process data. Second WorkSpaceRunner to mail attachment.

 

- FeatureWriter. Use Summary feature from FeatureWriter to initiate the next Transformer. I often use a Holder to prevent starting the Transformer after the FeatureWriter before all features are written.

I prefer the FeatureWriter because this way you can keep it in one Workspace.

The downside of using a FeatureWriter in server is that the field numFeaturesOutput in the job summary is not handled correctly. Using a classic writer this number tells the number of written features correctly.

Thanks for the answer.

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