Page Comparison

...

1. Starting the Dbvisit Replicate command console without a DDC file. This brings up an empty command console to run the setup wizard to initiate a new replication.
2. Run the start-console.sh or start-console.bat script to start the console with a DDC file. This is the preferred method after a replication has been configured through the setup wizard. The setup wizard creates the start-console.sh or start-console.bat scripts. 
3. Starting the Dbvisit Replicate command console with a DDC file. This connects to an existing replication and will show the progress and overview of the replication. From the command console, the replication can be changed, paused, stopped, new tables can be added, conflict handlers can be configured and current conflicts can be resolved.

1 - Starting the Dbvisit Replicate command console WITHOUT a DDC file

This brings up an empty command console to run the setup wizard to initiate a new replication.

On Windows:

There are several ways to start the Dbvisit Replicate command console:

...

The command console will start:

On Linux/Unix:

Start the dbvrep program without a DDC file:

dbvrep

2 - Starting the Dbvisit Replicate command console WITH a DDC file

This connects to an existing replication and will show the progress and overview of the replication. From the command console, the replication can be changed, paused, stopped, new tables can be added, conflict handlers can be configured and current conflicts can be resolved.

On Windows:

There are several ways to start the Dbvisit Replicate command console:

...

start-console.bat

On Linux/Unix:

There are several ways to start the Dbvisit Replicate command console:

...