General configuration process for Store and Forward replication

The following procedure illustrates the general process for configuring Store and Forward replication routes. This provides a high-level overview of what you have to do before and after, in addition to creating StoreAndForward records.

1. Set up doas_privileges records for the system.

   All systems have to have entries in the doas_privileges table for replication purposes. CreateCMXRepSubscriptions looks at doas_privileges records when making subscriptions for each of the systems.

2. Set up StoreAndForward records.

3. In ADE, double-click on the Custom Replication table.

   This opens the StoreAndForward Table Edit where you can add entries for all systems you want to communicate. Your desired routes need to be able to go in both directions. To configure a three-system model where ES owns the data and forwards it to the Backup through Main, you would create StoreAndForward records as shown below.

   

4. Open a Windows Command Prompt.

5. Execute the following command:

   savedata

6. Shut down the RealTime service on all RealTime servers.

7. On all RealTime servers except for the source, navigate to the following directory:

   <RealTime Server Name>\%DNADataRoot%\RealTime\database\cmxrepsql

8. Delete all subfolders.

9. Execute the following command:

   createCMXRepSubscriptions

10. Follow the procedure in CreateCMXRepSubscriptions.

11. Copy the following folder from the source directory, and paste it into the corresponding directory on all RealTime servers (for example, rtshostname1, rtshostname2, rtshostname3):

    <Source RealTime Server>\%DNADataRoot%\RealTime\database\cmxrepsql

12. Copy the following files from the source directory, and overwrite the same files in the other RealTime servers:

    <Source RealTime Server>\%DNADataRoot%\RealTime\database\INTEL_NT\*.init

13. Restart RealTime.

    You can verify that Store and Forward configuration is occurring as expected in NMC. Look at the System Synchronization node under RealTime for each system you have configured. The information under Synchronization should match the configuration you selected.

    In the three-system model described above, there would be no synchronization between ES and Back-up.