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. [. . . ] 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. You can collect all log files: default. pipeline1. groupwise-AppInterface. log default. pipeline1. groupwise. log default. pipeline1. mobility-AppInterface. log default. pipeline1. mobility. log engine. log configengine. log connectorManager. log PySQLPool. Query. log Or you can collect just the first five files in the list. The files are collected into a file named datasync_logs_yyyy-mm-ddThh. mm. ss. tar. gz. To run the Collect Logs tool: 1 In a terminal window, become the root user. 2 Change to the following directory: /opt/novell/datasync/tools 3 Run the following command: python CollectLogs. pyc 4 Enter yes if you want to collect all log files. A manifest. txt file is also created, which lists the files that have been included in the resulting . tar. gz file. When you submit the set of log files to Support, you also need to provide a GroupWise message ID of a message that has failed to synchronize, so that Support can use the Trace Log tool (traceLog. pyc) to trace the problem message. The output of the Trace Log tool includes the following sections to help Support diagnose the problem: Starting from GroupWise. . . =================================== From GroupWise Connector into Engine. . . ======================================= Inside Engine. . . Managing Your Synchronizer System 29 novdocx (en) 16 April 2010 ================ From Engine to Mobility Connector. . . ==================================== From Mobility Connector to Device. . . ==================================== Each section lists the message pertaining to the problem message for that segment of the synchronization process, enabling Support to pinpoint the source of the synchronization problem. 3. 5 Changing the Synchronizer Database Password To change the Synchronizer database password, you must change the password for datasync_user in three places: PostgreSQL (command on the command line) Sync Engine (setting in Synchronizer Web Admin) Config Engine (setting in a configuration file) 1 Reset the password for the PostgreSQL database: 1a In a terminal window on the Synchronizer server, log in as the root user. 1b Enter the following command: psql --user datasync_user datasync 1c Enter the current password for the Synchronizer database. 1d Enter the following command at the datasync> prompt: ALTER USER datasync_user WITH PASSWORD 'password'; Replace password with the new password for the Synchronizer database. 2 Reconfigure the Sync Engine to use the new password: 2a In Synchronizer Web Admin, click the Sync Engine. 2b In the Password field in the Database Settings box, specify the new Synchronizer database password. 3 Reconfigure the Config Engine to use the new password: 3a In the terminal window used for Step 1, change to the following directory: /etc/datasync/configengine 3b Edit the configengine. xml file in a text editor. 3c In the <database> section, replace the existing database password with the new password between the <password> tags. 4 Restart the Synchronizer services: 30 Novell Data Synchronizer Administration Guide novdocx (en) 16 April 2010 rcdatasync restart 5 (Conditional) If you want to change the Mobility Connector database password to match the Synchronizer database password, follow the instructions in "Changing the Mobility Connector Database Password" in "Mobility Connector Configuration" in the Groupwise Connector Installation and Configuration Guide. Managing Your Synchronizer System 31 novdocx (en) 16 April 2010 32 Novell Data Synchronizer Administration Guide novdocx (en) 16 April 2010 4 Managing Connectors 4 For an overview of general Data Synchronizer connector functionality, see: "Connectors" in "Data Synchronizer Product Overview" in the Novell Data Synchronizer Mobility Pack Installation Guide "Connectors" in "Data Synchronizer Product Overview" in the Novell Data Synchronizer Installation Guide Connector-specific information is located in the Installation and Configuration Guide (http:// www. novell. com/documentation/datasync_connectors1) for each connector. [. . . ] Commercially signed certificates should be automatically accepted by most mobile devices. 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. [. . . ]