User manual NOVELL DATA SYNCHRONIZER ADMINISTRATION GUIDE 07-2010

[. . . ] novdocx (en) 16 April 2010 AUTHORIZED DOCUMENTATION Administration Guide Novell® Data Synchronizer July 26, 2010 www. novell. com Novell Data Synchronizer Administration Guide novdocx (en) 16 April 2010 Legal Notices Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. [. . . ] When you list Connector Manager threads or Python threads in a terminal window, you cannot tell which Python thread is associated with the Connector Manager and which Python thread is associated with each connector. The Connector Manager log file lists each component and the PID number associated with each one. This can be very useful for troubleshooting. 26 Novell Data Synchronizer Administration Guide novdocx (en) 16 April 2010 3. 4. 6 Per-User Log Files Per-user log files (user_distinguished_name. log) report on problems that a specific user is having. Per-user logging is disabled by default. To enable it, see Section 3. 2. 3, "Enabling Per-User Logging, " on page 21. 3. 4. 7 Flatfile Connector Troubleshooting When data does not synchronize as expected, it can be challenging to determine which component in your Synchronizer system is the source of the problem. You can set up a Flatfile Connector to capture the data files that contain data from one application to see how that data is flowing through your Synchronizer system. For example, if data is not synchronizing successfully between GroupWise and a user's mobile device, you can set up a Flatfile Connector to determine where the problem lies. "Adding a Flatfile Connector" on page 27 "Troubleshooting Data Flow with the Flatfile Connector" on page 28 Adding a Flatfile Connector 1 In Synchronizer Web Admin, click Add Connector. 2 Specify a name for the Flatfile Connector, then click Add Connector. The Connector Type field defaults to flatfile. 3 Click the Flatfile Connector to display the Connector Configuration page. Managing Your Synchronizer System 27 novdocx (en) 16 April 2010 Note that the Flatfile Connector stores data files received from other connectors in the /tmp/ inbound directory and files that it sends to other connectors in the /tmp/outbound directory. By default, it scans its inbound and outbound directories every 20 seconds. 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 /tmp/inbound and /tmp/outbound directories. 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 /tmp/inbound directory. If the data file for the message has been received by the Flatfile Connector, the /tmp/ outbound directory contains a file named similar to the following example: 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 /tmp/outbound directory, it indicates that the failure 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 /tmp/outbound directory to determine whether the data file successfully passed from the mobile device, through the Mobility Connector, through the Sync Engine, and to the Flatfile Connector. 28 Novell Data Synchronizer Administration Guide novdocx (en) 16 April 2010 By using the Flatfile Connector, you can determine which log files are most likely to provide useful data for resolving the problem. 3. 4. 8 Collect Logs Tool As shown in the Section 3. 4. 1, "Log File Overview, " on page 25, Synchronizer log files are created in a variety of directories. The Collect Logs tool collects the most recent log files into a . tar. gz file for convenience when submitting log files to Support. [. . . ] 5 (Conditional) If your particular mobile device does not automatically accept the commercially signed certificate, follow the instructions in "Working with Self-Signed Certificates" on page 44 to configure your mobile device to use the certificate. 6 To use the same commercially signed certificate for Synchronizer Web Admin: 6a Change to the following directory: /var/lib/datasync/device/webadmin/server. pem 6b Back up the existing server. pem file Securing Your Synchronizer System 45 novdocx (en) 16 April 2010 6c Copy the certificate file received the certificate authority to /var/lib/datasync/ webadmin. 6d Rename it to server. pem. The other self-signed certificates that are created during installation are used for internal communication between Synchronizer services. You can replace these self-signed certificate files with the commercially signed certificate, but you do not see any difference in Synchronizer functionality. [. . . ]