January 28, 2013
NOTE:The 1.2.5 update pertains to the Mobility Pack. The Data Synchronizer product for use with connectors other than the Mobility Connector remains at version 1.2.4.
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.5 provides the following enhanced features compared to Mobility Pack 1.2.4:
Additional Device Operating Support: Windows Phone 8 is now supported.
Improved User/Group Management: Users and groups are now managed on a Synchronizer system level, rather than being associated with individual connectors.
Global Status Monitor: A preview version of the new Global Status Monitor is available for monitoring all aspects of your Synchronizer system in a single Web interface.
Device Quarantine: New devices can be automatically quarantined, so that they do not automatically connect to your Synchronizer system until you release them from the quarantine.
Automatic Device Removal: Unused devices can be automatically removed from your Synchronizer system.
Maximum Item Synchronization: You can control how much data synchronizes to mobile devices when users configure their devices to request synchronization for all email and calendar items.
MCheck Utility: The new MCheck utility helps you diagnose synchronization problem. MCheck gathers configuration settings for your Synchronizer system and verifies that the contents of the GroupWise Address Book and users’ mailboxes have synchronized to the Mobility Connector database.
Resource Mailbox Synchronization: You can synchronize resource mailboxes to your mobile device along with your own mailbox.
Simplified Logging Levels: The Info logging level now provides sufficient logging information for day-to-day usage. The Debug logging level should be used only for short-term periods of troubleshooting.
Synchronizer Web Admin Access by root User: If the LDAP server associated with your Synchronizer system is unavailable, you can log in to Synchronizer Web Admin using the root user name and password.
Anonymous Feedback: You can submit anonymous feedback about your Synchronizer system to Novell, in order to assist in ongoing efforts to improve Synchronizer performance.
WSTrust: The WSTrust single sign-on solution is now supported for use with Synchronizer Web Admin.
For a list of the documentation updates that have been made for Mobility Pack 1.2.5, see Section 9.0, Documentation.
For a list of the bugs that have been fixed in Mobility Pack 1.2.5, see the Mobility Pack 1.2.5 Bug Fix List.
Follow the instructions in this section if you are installing Mobility Pack 1.2.5 in order to create a new Synchronizer system.
The Mobility Pack 1.2.5 ISO is available from the Novell Downloads Web site. You use YaST to install Mobility Pack 1.2.5 from the downloaded ISO.
NOTE:If you need to uninstall and reinstall the Mobility Pack, follow the instructions in Mobility Pack Installation Guide. See also Section 5.14, Thorough Uninstallation Required.
On Novell Downloads, click to display Novell Patch Finder.
IMPORTANT:The Mobility Pack 1.2.5 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.5 ISO to a convenient temporary directory on the Synchronizer server.
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.5 ISO:
Under, click , then click .
Install the Mobility Pack as an add-on product.
Complete installation instructions are available in Mobility Pack Installation Guide.
Follow the instructions in this section to update an existing Synchronizer system.
Obtain the Mobility Pack 1.2.5 ISO from the Novell Customer Center.
Obtain the Mobility Pack 1.2.5 ISO from Novell Patch Finder on 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 take longer for a large database.
IMPORTANT:Do not cancel this process, even if it takes a very long time. Cancelling the process before it finishes can cause damage to the Mobility 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.
The process of updating your Synchronizer system to Mobility Pack 1.2.5 might take longer than previous updates. It is not unusual for the Update script to run for over an hour for a large database. Do not cancel the Update script. Wait for it to run to completion.
Updating the Mobility Pack software through an ssh connection is not recommended. An ssh connection can be interrupted before the update process finishes. An incomplete software update can leave the Synchronizer server in a non-working state.
When you install the Mobility Pack on SLES 11 SP2, you receive the following warning:
Import Untrusted GnuPG Key The following GnuPG key has been found in repository Unknown: Unknown
This is normal for an initial installation of the Mobility Pack on SLES 11 SP2. Clickto continue.
When you update a server where the Mobility Pack is installed from SLES 11 SP1 to SP2, you must select the Mobility Pack as an add-on product during the update process. This informs the update process that you want to retain the Mobility Pack on the updated server. For more information, see TID 7010339,
How to Upgrade Novell Data Synchronizer Mobility Pack Server to SLES 11 SP2 in the Novell Support Knowledgebase.
If you do not select the Mobility Pack during the update, the Mobility Pack RPMs are removed.
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 you can use the feature preview script to enable it.
Change to the following directory:
Run the script to enable task synchronization:
./previewfeature.sh --tasks --action enable
This enables task synchronization for all users.
Run the script to enable Status Monitor:
./previewfeature.sh --monitor --action enable
(Conditional) If you want to turn off a preview feature, use the disable action:
./previewfeature.sh --tasks --action disable ./previewfeature.sh --monitor --action disable
The Mobility Pack is supported in a virtual environment, but performance might be somewhat slower when it is 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.
This problem does not occur on SLES 11 SP2.
When you run the Mobility Pack Installation program, the Installation program displays the following error if you clicknext to the field or the field on the Data Synchronizer Settings page:
Connection to the LDAP server cannot be established A possible reason for the failed connection may be that your client is configured for TLS/SSL but the server does not support it Retry connection without TLS/SSL?
Clickto successfully browse for the user and group containers.
This error occurs regardless of whether you specified a secure LDAP port on the LDAP Server Settings page. The same error also appears if you clickon the Add Users and Groups page.
To avoid the error, type the information, rather than browsing for the LDAP users and groups.
You can configure a secure LDAP connection after installation, as described in Mobility Pack Administration Guide.
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 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 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.
The Mobility Pack repository should not be listed. If it is still listed, select it, then click.
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. In the drop-down list, select .
Under theheading, 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 YaST, click datasync, then click .. In the field, specify
Thelist should be empty. If any Data Synchronizer packages are still listed, uninstall them.
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
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.
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.
On the Connector Configuration Settings pages in Synchronizer Web Admin, each section of options has its ownbutton. When you modify a setting, use the button for that section of options to save your change. Using the button for a different section might not save your change.
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.
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.
Refer to the Readme for each connector on the Novell Data Synchronizer Connectors Documentation Web site.
For a list of the bugs that have been fixed in Mobility Pack 1.2.5, see the Mobility Pack 1.2.5 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 and the Novell Data Synchronizer Connector Documentation Web site.
Each Mobility Pack guide lists the documentation updates that have occurred since the previous release of the Mobility Pack:
In addition to the Mobility Pack documentation, the following resources provide additional information about the Data Synchronizer product:
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-2013 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.