1.0 Overview

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:

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.

5.1 Long Update Process

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.

5.2 Update through ssh Not Recommended

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.

5.3 Untrusted Key Warning

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. Click Import to continue.

5.4 Update Issue from SLES 11 SP1 to SLES 11 SP2

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.

5.5 Feature Preview Script

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.

5.6 Virtualization Support

The Mobility Pack is supported in a virtual environment, but performance might be somewhat slower when it is virtualized. Individual results might vary.

5.7 GroupWise Trusted Application Creation

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: Name, Location for Key File, and Name of Key File. Do not fill in any other fields. If you fill in additional fields, the trusted application does not work correctly with the GroupWise Connector.

5.8 YaST Proposal Error

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 clicked Next without providing the configuration information for your Synchronizer system. Instead of clicking Next, click Change > Mobility Pack Configuration, then provide the configuration as prompted. After you provide the configuration information, click Next.

5.9 YaST Hangs When Browsing Files

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

Certificate 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.

5.10 YaST Error When Configuring LDAP

When you run the Mobility Pack Installation program, the Installation program displays the following error if you click Browse next to the LDAP User Container field or the LDAP GroupWise Container 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?

Click Yes to 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 click Browse on the Add Users and Groups page.

To avoid the error, type the information, rather than browsing for the LDAP users and groups.

5.11 Required Python Package Version

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.

5.12 Mobility Pack Installation Program Fails on a 32-Bit/x86 Processor

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.

5.13 Unnecessary Traffic Created by Extraneous Users

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.

5.14 Thorough Uninstallation Required

The standard uninstallation procedures provided in Uninstalling the Mobility Pack in the 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 Software > Add-On Products.

The Mobility Pack should not be listed. If it is still listed, select it, then click Delete.

In YaST, click Software > Software Repositories.

The Mobility Pack repository should not be listed. If it is still listed, select it, then click Delete.

IMPORTANT:If you do not remove the existing Mobility Pack repository, you cannot successfully install the next version of the Mobility Pack software.

Under the Primary Functions heading, the Mobility Pack should not be listed. If it is still listed, select it. Review the Packages list for any packages that were not successfully uninstalled and uninstall them.

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.

6.3 Connector Configuration Settings

On the Connector Configuration Settings pages in Synchronizer Web Admin, each section of options has its own Save button. When you modify a setting, use the Save button for that section of options to save your change. Using the Save button for a different section might not save your change.

6.4 GroupWise Mobile Server Compatibility

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.

7.0 Connector Issues

7.1 General Connector Issues

7.1.1 Connector Does Not Stop

When you stop a connector in Synchronizer Web Admin and then start it again immediately, the status might indefinitely remain as Starting. 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 Stopped. 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:

rcdatasync-connectors restart

This should change the connector status in Synchronizer Web Admin from Starting to Stopped.

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.

10.0 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. 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.