Workspace Publishing with a Transformer
Instead of having a workspace send a notification at its completion, it could instead send a notification through a transformer called the FMEServerNotifier.
Here, a workspace author is sending an FME Server notification when a feature fails the conditions of a Tester transformer:
Notification properties are set in the transformer parameters. The parameters include those for connecting to FME Server, one for the topic to post to, and one for the message to be included.
Here the author intends to publish information to a topic called RoadInfo:
There are two advantages to issuing a notification this way, overusing the registration method:
The workspace can issue a notification during a translation, rather than at the end of it.
The workspace does not need to be run on FME Server to generate an FME Server notification. It will produce the same notification when run using FME Desktop.
The disadvantage is that you won't know whether the workspace completed successfully - or not - when the notification is issued.
| TIP |
| Just like triggering a topic at workspace completion, this method does not need a Publication to be created. In fact, assuming the topic already exists, this method can be set up without having to open the FME Server web interface at all! |
| Miss Vector says… |
|
I've got a workspace that reads 50,000 features, transforms them, and writes them out. If I want to send a single notification that the features have been read, which combination of transformers would be of most use?
1. Creator/FeatureWriter/FMEServerNotifier 2. Creator/FMEServerJobSubmitter 3. Creator/FeatureReader/FMEServerNotifier 4. FeatureHolder/Sampler/FMEServerNotifier |