You have two FeatureWriters, which one is writing the database you'd want to have those statistics for?
And how do you have your FMEServerEmailGenerator set up?
you need to pass the output of the ServerEmailGenerator into an FMEServerNotifier. In the notifier, you need to specify a topic to post the string to. On your FME Server you need to setup a topic and subscription to send an email
You have two FeatureWriters, which one is writing the database you'd want to have those statistics for?
And how do you have your FMEServerEmailGenerator set up?
The feature writer on the left is writing to the database, the feature writer on the right is for logging purposes. The FMEServerEmailGenerator parameters contain 2 email addresses and have the file geodatabase from the left hand geodatabase as an attachment. We don't (yet) have a FMEServerNotifier or a topic setup in the FME Server.
A further issue is that the output of the lefthand feature writer is writing to an existing filegeodatabase rather than first creating a geodatabase and then writing to it. Is that something that is done within the feature writer or is a separate transformer needed for this?
The feature writer on the left is writing to the database, the feature writer on the right is for logging purposes. The FMEServerEmailGenerator parameters contain 2 email addresses and have the file geodatabase from the left hand geodatabase as an attachment. We don't (yet) have a FMEServerNotifier or a topic setup in the FME Server.
A further issue is that the output of the lefthand feature writer is writing to an existing filegeodatabase rather than first creating a geodatabase and then writing to it. Is that something that is done within the feature writer or is a separate transformer needed for this?
Ok, I think I got what you mean.
It's probably a good idea to use an Emailer instead of the FMEServerEmailGenerator (because it can email directly, rather than creating a topic).
You'll need to take the Summary output of FeatureWriter_2 and join it on to the feature going into the Emailer, then you'll have access to its attributes so you can construct the email body.