Removing a Replication from Deployment
This tutorial removes a replication from the active replications.
Note:
You cannot remove all the active replications at once using this method.
Prerequisites
Install Adabas version 6.1.4 or above.
Install CONNX Data Integration Suite 1.1.2 or above.
Install Adabas Event Replicator for LUW.
Create an Adabas database with a DBID of 1 using the Adabas sample tables. For this example, we will use the Adabas sample table EMPLOYEES-NAT (File11).
Start the Adabas database.
An available SQL Server database. For this tutorial, we recommend that you create a database named Replication. Otherwise, you can use any existing SQL Server database.
Create a CDD containing the source and target databases. For this example, we will use the CDD Adabas to Relational Replication (our last opened CDD) that was created in the Performing a Simple Replication - Adabas to Relational Database tutorial.
Replicate (create and deploy) two source tables to the target database. In this example, we will assume that tables DBID1.dbo.ADABAS_FILE_11 and DBID1.dbo.ADABAS_FILE_11_AIC have been replicated to database SQLTarget.
Open the Adabas Event Replicator for LUW CDD and un-deploy a replication
1. Start the Replication Administrator. The main Adabas Event Replicator for LUW window with the information from the Adabas to Relational Replication CDD appears.
2. Select a replication to un-deploy. In this example, we will select ADABAS_FILE_11_AIC. On the Rep # 2 line, clear Active and click Deploy. The Active Replications Deployed to Controller message appears. Click OK. The updated Adabas Event Replicator for LUW window appears.
Although ADABAS_FILE_11_AIC still appears in the window, it will not be deployed since Active is not selected.
Validate the un-deploy
Click the Deployed Replications tab. Verify that the only entry is for DBID1.dbo.ADABAS_FILE_11.
This completes removing a replication from deployment. You can do inserts, updates, and deletes against ADABAS_FILE_11 in database 1 and the changes will replicate to your SQL Server database.