Federation Manager Guide › Failover Support for Federation Manager › Maintaining Configuration Changes in a Failover Environment › Keep the Configuration Consistent for Each Federation Manager System

Keep the Configuration Consistent for Each Federation Manager System

If you make any configuration changes to Federation Manager, always administer these changes to the primary Federation Manager system then export the configuration to the secondary machine.

Be aware of the following in regard to configuration changes:

• UI-managed data that is stored in the database is available to the secondary system because the primary and secondary systems share the same database. Despite the shared database, changes made using the primary system's UI may not be immediately available to the secondary system because there may be a delay before the secondary system's policy engine picks up the changes.

  Note: The key database is also managed by the UI, but it is stored on the system's hard drive and therefore, not shared.

• Some Federation Manager configuration changes require a restart of the system. If you make a change to the primary system and this change requires a restart, you must restart the secondary system also.
• Administration should always be performed on the same primary system. You can disable UI administration on the secondary machine to enforce this practice.

  To disable UI administration on the secondary system

  1. Log on to the Federation Manager UI.
  2. Select Infrastructure, System Settings.

     The Configure System Settings dialog displays.

  3. Click Disable Administration in the UI Settings group box.

     A message appears asking you to confirm the action.

  4. Click Yes to disable UI administration.

     An Administration Disabled dialog displays while all other parts of the UI become unavailable. This dialog lets you re-enable administration.