We are using FME to replicate spatial records between databases. The replication workbench is dynamic and being triggered by Informatica Power Center via async web service call. We have a dedicated engine for Replication because these calls need to stay in order. Does anyone have any best practices on making sure the jobs in the queue do not start running if one 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.
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.
+59- Celebrity
- 3697 replies
Two ideas come to mind:
- Make use of Notifications. Success of workpace1 triggers a notification which in turn triggers a 2nd workspace to run. Failure of workpace1 triggers another notification for error handling/reporting (or nothing at all)
- Use FMEServerWorkspaceRunners from a master workspace, you can then set up that master workspace to handle success or failure of the child workspaces.
The 2018 FME Server Authoring course has an excercise covering that 2nd approach.