To ensure that configuration data is not unintentionally overwritten, content federation systems with high availability and disaster recovery requirements should use an active-passive server configuration for the Federation Administration application deployment.
In an active-passive server configuration, all content federation administrators are directed to the same instance of the Federation Administration application. If the active server fails, the traffic is redirected to the passive server, which then becomes the active server.
Configuration information is stored in the IBM® FileNet® CFS for Content Integrator properties file and in the Federator database. Configuration changes are written to both the properties file and the database. Store the properties file on a mirrored disk and point both the active and passive content federation installations to this file.
In an active-active configuration, traffic is load balanced and spread evenly across the servers. If a server fails, all traffic is directed to the remaining servers. IBM FileNet CFS for Content Integrator does not support an active-active configuration.