Switching from Test to Production
Typically, a CDD with replications will be created in a test or development environment. Once development and testing of the replications is done, the replications need to be rolled out to the production environment. This can be achieved by making a copy of the CDD and then modifying the server names and/or the database ID's in the CDD.
The following example is going to have a CONNX Data Dictionary that is replicating tables from a test Adabas Nucleus to a test Oracle database. In order to transition the data dictionary from a test to production environment, the two environments must have table names and structures that are identical to what was in the test databases.
How to move an Event Replication Data Dictionary from a test to production environment:
1. As a good practice with any modifications, make a back up copy of the CONNX Data Dictionary that is going to be modified.
2. Close the Replication Administrator and open the Data Dictionary in the Data Dictionary Manager. Select the Adabas Nucleus in the container list on the left side and the Database Info tab on the right will show the Adabas Database ID.
3. In the field for ADABAS Database ID, change the id number from the test nucleus to the production nucleus.
4. Select the Oracle container in the list on the left and the Database Info tab on the right will show the Physical Database Name of the Oracle server.
5. Change the Physical Database Name from the test server to the production server.
6. Change the Database Account Management entries. This is mandatory for Oracle Servers.
a. Click Security -> Database Account Management in the menu bar.
b. Change the Server Name and if necessary, the UserID and Password under the oracle database column for each User/Group in the dropdown list. Click Done when finished.
7. Save the changes in the CONNX Data Dictionary Manger and close the data dictionary.
8. Open the CONNX Data Dictionary that was just modified in the Replication Administrator.
The Replication Administrator will detect the changes to the servers and prompt the user if these changes were intentional. Select Yes to both change questions and the Replications will be updated to use the new servers. Pressing No will remove the invalid replications.
9. Click Servers -> Config Servers and change the Replication Server to the production replication server.
10. Select Done when finished and the Replications are ready for deployment to the production environment.