December 12, 2011
The Novell Data Synchronizer Mobility Pack creates or updates a Synchronizer system that consists of the Synchronizer services, the GroupWise Connector, and the Mobility Connector on a single server. This Synchronizer system enables you to easily synchronize GroupWise data to mobile devices.
Mobility Pack 1.2.1 provides the following enhanced feature compared to Mobility Pack 1.2:
Failed Delivery Notification: If you send an item from your mobile device and it fails to reach your GroupWise system for any reason, you receive an e-mail on your mobile device notifying you of the delivery failure. One cause for delivery failure is that you have exceeded your GroupWise mailbox size limit as set by your GroupWise administrator.
Archived Item Handling If your GroupWise system is backed up using an archive solution that employs GroupWise stubbing, GroupWise items synchronize to mobile devices when they are archived and stubbed, because they have been modified by the archive solution. You can configure the GroupWise Connector to drop stubbed items so that they do not synchronize to mobile devices.
Feature Preview Script: Update 1 includes preliminary functionality for synchronizing tasks that will be available in the next major release. You can enable the functionality using the previewfeature.sh script.
Updates to the Mobility Pack are released regularly. Some updates are major version updates, such as Mobility Pack 1.1.x to Mobility Pack 1.2. Other updates are minor updates to an existing version, such as Mobility Pack 1.2 to Mobility Pack 1.2.x.
For a list of the bugs that have been fixed since Mobility Pack 1.2, see the Novell Data Synchronizer 1.2.1 Bug Fix List.
See the system requirements for each component of your Mobility Pack installation:
Follow the instructions in this section if you are installing Mobility Pack 1.2.1 in order to create a new Synchronizer system.
The Mobility Pack 1.2.1 ISO is available from the Novell Downloads Web site. You use YaST to install Mobility Pack 1.2.1 from the downloaded ISO.
NOTE:If you need to uninstall and reinstall the Mobility Pack, follow the instructions in
Uninstalling the Mobility Pack in the Novell Data Synchronizer Mobility Pack Installation Guide. See also Section 5.10, Thorough Uninstallation Required.
On Novell Downloads, click .
IMPORTANT:The Mobility Pack 1.2.1 software is located in thelist, not the list.
Select, then click .
Under, click .
Click, then follow the online instructions to download the Mobility Pack 1.2.1 ISO to a convenient temporary directory on the Synchronizer server.
Continue with Installing Mobility Pack 1.2.1 to Create Your New Synchronizer System.
Make sure that the Linux server where you plan to install the Mobility Pack meets the system requirements.
If a Web server is currently running on the Synchronizer server, stop it, and preferably disable it.
Use YaST to install the Mobility Pack 1.2.1 ISO:
Under, click , then click .
Install the Mobility Pack as an add-on product.
Complete installation instructions are available in
Installing and Setting Up a Data Synchronizer System in the Novell Data Synchronizer Mobility Pack Installation Guide.
For additional planning assistance, see the Data Synchronizer Mobility Pack Best Practices Wiki.
Follow the instructions in this section to update an existing Synchronizer system.
Obtain the Mobility Pack 1.2.1 ISO from the Novell Customer Center.
Obtain the Mobility Pack 1.2.1 ISO from the Novell Downloads Web site.
In YaST, run Patch CD Update to install the updated Mobility Pack ISO to your Synchronizer system.
Make sure that PostgreSQL is running:
Run the Mobility Pack Update script:
For some version updates, the update process finishes quickly. However, the update process can be more lengthy for a large database.
Restart the Synchronizer services and PostgreSQL:
Stop the Synchronizer services:
Verify that all Synchronizer services have stopped:
ps -eaf | grep datasync
Start the Synchronizer services:
Verify that update has been installed:
The version number is displayed at the bottom of the main Synchronizer Web Admin page.
For more detailed instructions, see
Mobility Pack Update in the Novell Data Synchronizer Mobility Pack Installation Guide.
Section 5.6, YaST Hangs When Browsing Files in the Installation Program
Section 5.8, Mobility Pack Installation Program Fails on a 32-Bit/x86 Processor
Section 5.9, Unnecessary Traffic Created by Extraneous Users
The feature preview script (previewfeature.sh) lets you enable functionality that is currently under development but not yet officially released and supported. Such functionality is disabled by default, but can be enabled using the feature preview script.
Some task synchronization functionality that will be available in the next release is currently available for preview.
Change to the following directory:
Run the following script to enable task synchronization:
./previewfeature.sh --tasks --action enable
This enables task synchronization for all users.
(Conditional) If you want to turn task synchronization off again, use the following command:
./previewfeature.sh --tasks --action disable
A Synchronizer system can communicate with only one GroupWise system. Creating multiple connectors of the same type on a single Synchronizer server is not supported. For more details, see
Synchronizer System Configuration in
Mobility Pack Product Overview in the Novell Data Synchronizer Mobility Pack Installation Guide.
The Mobility Pack is supported in a virtual environment, but performance might be somewhat slower when virtualized. Individual results might vary.
Before you run the Mobility Pack Installation program, you must create a GroupWise trusted application so that the GroupWise Connector can log in to a GroupWise Post Office Agent (POA) in order to access GroupWise mailboxes without needing personal user passwords. When you set up the GroupWise Connector as a trusted application, you need to fill in only three fields in the Create Trusted Application dialog box in ConsoleOne: , , and . Do not fill in any other fields. If you fill in additional fields, the trusted application does not work correctly with the GroupWise Connector.
When you run the Mobility Pack Installation program in YaST, you might see the following error:
The proposal contains an error that must be resolved before continuing
This error indicates that you clickedwithout providing the configuration information for your Synchronizer system. Instead of clicking , click , then provide the configuration as prompted. After you provide the configuration information, click .
When you run the Mobility Pack Installation program on SUSE Linux Enterprise Server (SLES) 11 SP1, the Installation program might hang if you browse to and select a file. This can occur if you try to browse to and select any of the following files during installation:
Mobility Pack ISO file
GroupWise trusted application key file
As a workaround, type the full path and filename for the file instead of browsing to it.
If you already have Python packages installed on the server where you are installing the Mobility Pack, the Installation program needs to update the existing packages, rather than install new packages. This does not happen by default.
When you run the Installation program, you are prompted if packages need to be updated. Enter 1 for Solution 1 to update each package.
The Mobility Pack must be installed on a server with a 64-bit/x86 processor. If you try to install it on a server with a 32-bit/x86 processor, the Mobility Pack Installation program does not detect the problem. It tries to run, but it cannot run correctly.
If the behavior of the Installation program does not match the installation instructions provided in the Novell Data Synchronizer Mobility Pack Installation Guide, make sure that you are installing the Mobility Pack on a server that meets the documented system requirements.
There are currently no plans to make the Mobility Pack available in a 32-bit version.
When you add users to your Synchronizer system, data is automatically synchronized from GroupWise to the Mobility Connector before users connect their mobile devices to your Synchronizer system. Do not add users to your Synchronizer system who do not have mobile devices. Extraneous users create unnecessary synchronization traffic in your Synchronizer system.
The standard uninstallation procedures provided in
Uninstalling the Mobility Pack in the Novell Data Synchronizer Mobility Pack Installation Guide occasionally fail to completely uninstall the Mobility Pack because of various server-specific issues. When the Mobility Pack software is not completely uninstalled, the next installation does not proceed normally. For example, you might encounter problems configuring LDAP access during installation. To ensure that the Mobility Pack software has been completely uninstalled, perform the following checks:
In YaST, click The Mobility Pack should not be listed. If it is still listed, select it, then click ..
In YaST, click Mobility Pack repository should not be listed. If it is still listed, select it, then click .. The
IMPORTANT:If you do not remove the existing Mobility Pack repository, you cannot successfully install the next version of the Mobility Pack software.
In YaST, click the Mobility Pack should not be listed. If it is still listed, select it. Review the list for any packages that were not successfully uninstalled and uninstall them.. In the drop-down list, select . Under the heading,
In YaST, click datasync, then click . The list should be empty. If any Data Synchronizer packages are still listed, uninstall them.. In the field, specify
Log in as root in a terminal window, then check for Data Synchronizer RPMs:
rpm -qa | grep datasync
If any Data Synchronizer RPMs are still installed, uninstall them:
rpm -e rpm_name.rpm
Make sure that none of the following directories still exist on your server:
/opt/novell/datasync /etc/datasync /etc/init.d/datasync* /var/lib/datasync /var/log/datasync /var/run/datasync /var/lib/pgsql
If any of these directories still exist, delete them.
After performing all these checks, reboot the Synchronizer server.
Remove the Synchronizer certificate from any workstations where you have run Synchronizer Web Admin. For example, in Firefox, click DataSync Web Admin, then click .. Select the certificate named
Section 6.3, Users and Groups Not Displayed Correctly in Synchronizer Web Admin
Occasionally, when you shut down the Synchronizer services, one or more services fails to shut down. A message notifies you of the problem. To resolve the problem:
Use the following command to identify the processes that did not shut down:
ps -eaf | grep python
(Conditional) If the Synchronizer services are the only Python processes running on the server, use the following command to kill all of them:
killall -9 python
(Conditional) If non-Synchronizer Python processes are running on the server, use the following command to kill each individual Synchronizer process:
kill -9 pid
Replace pid with the process ID of each Synchronizer Python process, as listed in Step 1.
When you are finished killing Synchronizer processes, repeat the ps command to verify that all killed processes have actually shut down.
If you add a user to a connector as part of an eDirectory group, and if you subsequently move the user from one eDirectory container to another, the user is removed from the connector because the user’s context has changed. There is currently no mechanism for the connector to detect this change.
As a workaround:
Delete the user from the eDirectory group.
Wait until the user has been removed from all connectors.
Add the user back to the eDirectory group, so that the user’s new context is available to the connectors.
When you add or delete a large number of users or groups in Synchronizer Web Admin, the Manage Users page or the Manage Groups page might not correctly display the presence or absence of the users or groups. Refresh the page in your browser to correctly display the users or groups.
After you add a large number of users to the GroupWise Connector, the responsiveness of Synchronizer Web Admin might diminish each time you restart the GroupWise Connector. For example, it might take longer to log in to Synchronizer Web Admin, or you might not be able to navigate easily between pages while the GroupWise Connector is starting. This occurs because the GroupWise Connector verifies all of the users each time it starts. After the user verification process is completed, Synchronizer Web Admin behaves normally.
On the Connector Configuration Settings pages for the GroupWise Connector and the Mobility Connector, if you set and save general connector settings, then set and save connector-specific settings, the general connector settings are not actually saved. However, if you set and save connector-specific settings, then set and save general connector settings, all changed settings are saved as expected.
The Novell Data Synchronizer Mobility Pack is the replacement for GroupWise Mobile Server (GMS). These two synchronization solutions can coexist successfully, as long as users are transitioned from GMS to Synchronizer in a timely manner. An issue with GMS can cause a user whose mobile device is configured to use both synchronization solutions to occasionally receive a large quantity of extraneous items. As you add users to Synchronizer, you should delete them from GMS. You can continue to run GMS indefinitely to support users with older mobile devices that are not supported by Synchronizer.
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. When the connector starts again, the administrator does not need to take any additional action.
When you stop a connector in Synchronizer Web Admin and then start it again immediately, the status might indefinitely remain as. 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 . 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:
Restart the Connector Manager on the command line:
This should change the connector status in Synchronizer Web Admin fromto .
Start the connector in Synchronizer Web Admin.
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.
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 on additional servers 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.
Refer to the Readme for each connector on the Novell Data Synchronizer Connectors Documentation Web site.
For all bugs that have been fixed since Novell Data Synchronizer Mobility Pack 1.2, see the Novell Data Synchronizer 1.2.1 Bug Fix List.
If you have access to Novell Bugzilla, you can look up the bug numbers for more information about each bug.
The Mobility Pack documentation is available at the Novell Data Synchronizer Documentation Web site:
Mobility Pack Readme
Mobility Pack Installation Guide
Data Synchronizer System Administration Guide
Data Synchronizer connector documentation is available at the Novell Data Synchronizer Connector Documentation Web site
Connector Quick Starts
Connector installation and configuration guides
In addition to the Data Synchronizer product documentation, the following resources provide additional information about Data Synchronizer:
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. Further, Novell, Inc. 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.
Further, Novell, Inc. 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. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export, or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. Please refer to the Novell International Trade Services Web page for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.
Copyright © 2010-2011 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.
For Novell trademarks, see the Novell Trademark and Service Mark list.
All third-party trademarks are the property of their respective owners.