CONNX Data Integration Suite 14.8.0 | Adabas Event Replicator for LUW | Using Adabas Event Replicator for LUW | Deploying the Event Replication
 
Deploying the Event Replication
Deploying the event replication includes:
*Opening a CONNX Data Dictionary (CDD).
*Marking replications to be deployed as active.
*Deploying active replications to the replication controller.
Deploy the event replication to begin actively replicating your source data to the target databases. After deploying the event replication, you will be able to check server status.
All changes made using Adabas Event Replicator for LUW must be deployed to the appropriate replication server for them to take effect.
Note: 
If the event producer and controller were installed on different machines, start the message queue on both machines (Windows or UNIX) before deploying a replication.
*To deploy a replication:
1. Open the Adabas Event Replicator for LUW CDD.
2. Mark the Active checkboxes for the replications you want to deploy.
3. Validate that the active replications are ready to be deployed with the Validate Active button.
4. Click Deploy.
A status dialog will appear displaying each step and status of the deployment process. When the deploy is complete there will be a message showing that the system is replicating or processing initial states. If there are any errors during the deploy process, they will be displayed in this message box. For more information on status after a deploy, go to the Server Status tab.
The Ada # column will be blank until the deploy has completed. In an Adabas to Adabas replication environment, the Ada # relates to the ID column from the Adabas adaopr command when using the display=replication option. For more information about the adaopr command, and the replication related options, please see the Adabas Utilities documentation.
Note: 
Starting with version 12 SP3, Adabas to Adabas replications can no longer be undeployed by unchecking the Active checkbox and redeploying. To undeploy an individual Adabas to Adabas replication, use the UnDeploy Selected button on the Deployed Replications tab