Novell Data Synchronizer Mobility Pack Update 1
7
7 Connector Issues
Section 7.1, “General Connector Issues,” on page 7
Section 7.2, “Connector-Specific Issues,” on page 8
7.1 General Connector Issues
“User Deletion” on page 7
“Connector Does Not Stop” on page 7
“Multiple Instances of the Same Connector” on page 7
7.1.1 User Deletion
In order to delete users from a connector, the connector must be running. If the connector is not
running, some user event data is not properly deleted.
7.1.2 Connector Does Not Stop
When you stop a connector in Synchronizer Web Admin and then start it again immediately, the
status might indefinitely remain as
Starting
. This can happen because the connector did not
completely stop before you tried to restart it. The connector might have been completing a polling
cycle before shutting down, even though Synchronizer Web Admin displayed the status as
Stopped
.
When you try to start a connector that is still shutting down, it cannot start normally.
To restart the connector when this situation has occurred:
1
Restart the Connector Manager on the command line:
rcdatasync-connectors restart
This should change the connector status in Synchronizer Web Admin from
Starting
to
Stopped
.
2
Start the connector in Synchronizer Web Admin.
3
Start any other connectors that stopped as a result of restarting the Connector Manager.
Some connectors restart automatically when the Connector Manager restarts.
If this problem occurs repeatedly, wait a few seconds between the time when you stop the connector
and when you start it again to allow the connector to shut down completely before restarting.
7.1.3 Multiple Instances of the Same Connector
Synchronizer Web Admin allows you to manually create multiple instances of the same connector.
However, this configuration is not currently supported.
If you have more users than a single connector can service, you can install one or more additional
instances of the Mobility Pack until all users are being successfully serviced. Users can be organized
on multiple instances of the Mobility Pack based on various schemes such as the location of the
users, the location of the synchronized applications, or the desired quality of service (executives vs.
regular employees, for example). Instances of the Mobility Pack do not need to mirror the structure
of your GroupWise system.
