Watch a Video

How does it work?

• The first step/workspace in the workflow is submitted as a job in asyncronous mode.
  • In each of the step workspaces, if an error is encountered the workspace logs uniquely identifiable messages using a Logger transformer (e.g. MyWorkflow 2 - some error message).
  • When the job completes successfully, a message is sent to the Notification Server's JOB_SUCCESS topic.
• A 'controller' workspace receives the success message, looks through the log file to determine if any error messages were logged and then:
  • if there is an issue in one of the workflow steps, then a message can be sent to the Notification Server so that an email can be sent with details about the issue or
  • if there are no issues, then the next step/workspace in the workflow can be performed by submitting a job to FME Server.

Setup

• A controller workspace (using a custom format) is published to FME Server and registered with the Subscriber service to monitor the JOB_SUCCESS topic.
• A Topic and Subscription are created, in order to email error messages, which are discovered by the controller workspace.

Limitations

• Currently, the jobs only send a message to the JOB_SUCCESS/JOB_FAILURE topics if they are submitted asyncronuosly (e.g. by providing an email address in the Web UI). This means that an HTTPFetcher must be used to submit the next step instead of the FMEServerJobSubmitter transformer.
• Also, there is no way to select a separate topic for the step workspaces to notify on. So the controller workspace will process all jobs submitted asynchronously. Although this processing is quite quick.