Novell DATA SYNCHRONIZER - ADMINISTRATION GUIDE 07-2010 Administration Manual page 28

Note that the Flatfile Connector stores data files received from other connectors in the
inbound
By default, it scans its
4 Click Users, then add the user who is having synchronization problems to the Flatfile
Connector.
5 Return to the main Synchronizer Web Admin page, then start the Flatfile Connector.
This creates the
Troubleshooting Data Flow with the Flatfile Connector
1 Have the user with the synchronization problem send a message from GroupWise.
2 On the Synchronizer server, change to the
If the data file for the message has been received by the Flatfile Connector, the
outbound
default-pipeline1-groupwise-source-soapbridge-alphanumeric_string
The existence of this file shows that the data passed from GroupWise, through the GroupWise
Connector, through the Sync Engine, and to the Flatfile Connector. This indicates that the same
data should also have been received the Mobility Connector. If the data does not arrive on the
mobile device, it shows that the problem resides in the Mobility Connector.
If a data file does not appear in the
occurred in the GroupWise Connector or the Sync Engine, meaning that the Mobility
Connector never received the data.
3 Have the user with the synchronization problem send a message from the mobile device.
4 Again, check the
passed from the mobile device, through the Mobility Connector, through the Sync Engine, and
to the Flatfile Connector.
28 Novell Data Synchronizer Administration Guide
directory and files that it sends to other connectors in the
and
inbound
and
/tmp/inbound
directory contains a file named similar to the following example:
/tmp/outbound
directories every 20 seconds.
outbound
directories.
/tmp/outbound
directory.
/tmp/inbound
directory, it indicates that the failure
/tmp/outbound
directory to determine whether the data file successfully
/tmp/
directory.
/tmp/outbound
/tmp/