Creating a Bidirectional Replication Environment

Define an environment where data is updated at multiple locations and replicated on each site.

1. Identify the servers and databases that will be part of the bidirectional replication environment.
2. Select a replicate server, then a corresponding database, and click Add.

   The corresponding data server.database connection displays in the Connections list.

   Repeat this step for each replicate server and replicate database pair you need in your environment. Click Next.

3. Enter the user name and password of the maintenance user. If the maintenance user does not exist, the wizard creates one for you. Accept the defaults, or enter your own values. Click Next.

   All selected connections will use this maintenance user login.

4. Select the user name and password that the RepAgent will use to connect to Replication Server. If the RepAgent user does not exist, the wizard creates one for you, assigning a default name and password. Accept the defaults, or enter your own values. Click Next.

   All connections will use this RepAgent login.

5. Specify how replicated tables will materialize:

   • Create Subscription Without Materialization – use this method if the primary data is already loaded at the replicate and updates are not in progress.

   • Define Subscription for Bulk Materialization – in this method, a subscription is initialized by a user-specified mechanism outside the replication system.

6. If you chose Define Subscription for Bulk Materialization, click Use Dump Marker in the Transaction Log to use dump and load coordination. Click Next.
7. Click Finish if everything looks correct in the information summary of replication environment. Otherwise, click Back to return to an earlier window and change the replication environment information. Then, return to the final wizard window and click Finish.
   At the end of the configuration, Replication Manager creates the following replication objects:

   • Physical connections

   • A database replication definition for the primary database

   • One or more database subscriptions for each of the replicate databases

   • Maintenance user in Adaptive Server Enterprise servers