It would be great to able to disable certain automations in FME Server when a restore from backup is completed. For example Publications, Subscriptions and Schedules. This would ensure that FME Server Workspaces that receive and send emails will not cause conflicts when moving from one install of server to the next.
Archived
Option to Disable FME Server Automations on FME Server Restores
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.
+13- Safer
I had a discussion with a customer today related to this.
It would be really nice for the Restore Wizard to automatically put these into 'Standby' and provide feedback that these Notifications & Schedules have been set to Standby. The Wizard could give the user options to enable these at the time of restore or keep them in 'Standby' mode. If left in 'Standby' then this would allow the user to ensure any other previous FME Server System is first brought offline before enabling them.
It should be easy to identify these were enabled in the previous system... setting them to a new state like 'Standby' (vs disabled|Enabled) would help identify them after the fact.
+4- Contributor
I agree with this need. As a current user I have to install/replicate a whole FME Setup for various purposes (testing new processes, testing new setup, testing new version) and it is really a big time sink when migrating an install means spending a few hours disabling items/functions so that they dont cause conflicts with the production system and trying to make it so the new test system does not have any errors coming up anywhere.
This will help speed up testing a new version and deploying a new system because it would allow deployment to happen in stages as the admin enables functions (notifications, subscriptions, connections, etc..)
