Grass Valley NewsShare v.5.5 - Manual (Page 113)

Digital News Production 111
5. Repeat either Step 2a or 2b for each DNP machine on the shared volume that
runs FeedClip, NewsEdit, NewsQ, or the SmartBin Service. Do not modify
conform servers, which in current releases do not connect to the shared
database. If you're modifying several machines, it may be convenient to
create a Registry script similar to that shown in the example, deposit it on the
shared volume, then double-click run it at each machine.
Dropping the Old News Database From the
FSMs
This step is important in that substantial replication functions of the Failover
Monitor service will not be disabled unless the News database is dropped from
the FSMs. Note that this a is cleanup task on the former hosts of the News DB:
Do not drop the transplanted database from the DSM.
To remove the old news database:
1. Follow standard procedures to again remove the primary FSM from service.
(The back-up FSM should not have been returned to service yet.) At this
point, both FSMs should be powered on and both Failover Monitor services
should be stopped.
2. On each FSM, follow the Remove (for complete uninstall) procedure
described in Appendix A.
3. Follow standard procedures to return the FSM pair to active primary-backup
service.
Verifying Operation
Perform various operations to confirm that all DNP machines (NewsEdits,
Profiles, etc.) function correctly. Winking should be tested, in that it touches
several interoperation dependencies.