Preparation for setting up replication environment

All server clocks are synchronized.

Only one user configures the replication servers at any point.

No other users should be logged into any of the other Bravura Security Fabric servers while the replication environment is configured.

The product administrator who is configuring replication has the right to maintain servers.

All servers have the same instance name and virtual directories.

All servers use the same Connector Pack version and Connector Pack type.

All servers have the same installed components.

All replication configuration changes are made from the primary server; that is, the server that runs auto-discovery.

Once auto-discovery has run on the primary server, the gathered information is replicated to other nodes. This may take some time. Concurrent changes can cause race conditions in a replicated environment.

The Microsoft SQL versions are the same on all servers, including the same edition and service pack level.

When upgrading Microsoft SQL, schedule the upgrades on all databases as close together as possible, because replication will be stopped while the application nodes are served by different version databases.

The backend database must be available when a Bravura Security Fabric node is running; see Installing and configuring Microsoft SQL Server for a list of installation and monitoring requirements.

The email server configuration is manually set up on each node in the replication environment.

All servers use the same Bravura Security Fabric license.

All nodes are installed with the same directory paths, psadmin user and password.

Using the idmsetup.inf file from the main server to aid the installation of the replication node.