Before you deploy a configuration or configuration changes to a destination environment, manually apply any DDL changes to the destination databases that are necessary to make the databases match.

Ensure that all components in both environments use the same version of Data Replication. If one environment uses an earlier Data Replication version, upgrade that Data Replication installation.

In the

DataReplication_installation

/uiconf/default.cfg file on the computer where you use the Server Manager CLI, set the use_default_values_during_saving parameter to true:

use_default_values_during_saving=true

If the source tables that you mapped in the configuration do not have primary keys, the Replication Configuration CLI creates a virtual index for these tables, by default, to properly process Updates and Deletes. The index includes all of the table columns. Informatica recommends the default setting of 3 to process the commands for deploying configurations.

You can replace the schema names from the original environment during the initial configuration deployment. However, do not define schema replacement rules in the deployment properties file that replace a single schema name with multiple schema names or that replace multiple schema names with a single schema name. When defining schema replacement rules, ensure that each schema in the original environment corresponds to a single schema in the destination environment.

The deployment process uses the login credentials of the prodSmUser user that are specified in the deploy.properties file to connect to the Server Manager in the destination environment. For a remote deployment, these login credentials include the password that is specified in the

passwd

parameter of the

deploy config

or

redeploy config

command. These login credentials cannot be in use by any running Data Replication application in the destination environment during the deployment. Before you deploy a configuration or configuration changes to a destination environment, ensure that no Data Replication applications are running under these login credentials. Also, ensure that the login credentials remain inactive in the destination environment throughout the deployment process.

If you make DDL changes to tables or columns in the destination database after an initial deployment of a configuration, the DDL changes will be lost when you redeploy the configuration unless you perform one of the following actions:

Make the same DDL changes to the database in the original environment before you redeploy the configuration.
In the
redeploy config
command, use the -r or -e parameter, or both parameters. If you use the -m or -a parameter in the
redeploy config
command, the DDL changes to the destination databases will be lost.