1.2 Managing the Synchronizer Services Individually

If you manage the Synchronizer services individually, they should be started in the following order:

The Synchronizer services should be stopped in the following order:

You can start and stop Web Admin at any time, as long as the other Synchronizer services are running.

Each Synchronizer service has its own set of commands:

1.2.1 Managing the Sync Engine

Use the following command as root to check the status of the Sync Engine:

rcdatasync-syncengine status

Use the following commands as root to manually start and stop the Sync Engine:

rcdatasync-syncengine start
rcdatasync-syncengine restart
rcdatasync-syncengine stop

1.2.2 Managing the Config Engine

Use the following command as root to check the status of the Config Engine:

rcdatasync-configengine status

Use the following commands as root to manually start and stop the Config Engine:

rcdatasync-configengine start
rcdatasync-configengine restart
rcdatasync-configengine stop

1.2.3 Managing the Web Admin Service

Use the following command as root to check the status of the Web Admin service:

rcdatasync-webadmin status

Use the following commands as root to manually start and stop the Web Admin service:

rcdatasync-webadmin start
rcdatasync-webadmin restart
rcdatasync-webadmin stop

1.2.4 Managing the Connector Manager

Use the following command as root to check the status of the Connector Manager:

rcdatasync-connectors status

Use the following commands as root to manually start and stop the Connector Manager:

rcdatasync-connectors start
rcdatasync-connectors restart
rcdatasync-connectors stop