Use the

deploy config

command to deploy an entire configuration to a local or remote Server Manager Main server. The

deploy config

command is equivalent to the

Full

deployment type in the Data Replication Console. You must perform a full deployment the first time you deploy a configuration.

After the initial deployment, you can use the

redeploy config

command to deploy configuration changes. The

redeploy config

command is equivalent to the

Partial

deployment type in the Data Replication Console.

In the following common scenarios, perform a full deployment:

Deploy a configuration from a test environment to a remote production environment.
Deploy a configuration to the local Server Manager Main server to quickly generate multiple configuration files based on the original configuration.
Deploy a configuration to the local Server Manager Main server to configure a replication job that replicates data from multiple sources to a single target.

The Data Replication documentation uses the following terms to refer to the configurations and environments that are involved in the deployment process:

Destination environment
. The environment to which you deploy a configuration or configuration changes. The deployment destination can be a remote production environment or a local environment that uses the same Server Manager Main server.
New configuration
. The copy of the original configuration in the destination environment.
Original configuration
. The configuration that you deploy from the original environment.
Original environment
. The environment from which you deploy the original configuration.

The Server Manager CLI uses the Replication Configuration CLI to update the replication configuration in the destination environment immediately after the deployment. The Replication Configuration CLI updates source and target schemas and object IDs. By default, the Replication Configuration CLI also creates virtual indexes in the configuration for the source tables that do not have primary keys.