The Novell Data Synchronizer Mobility Pack creates a new 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.
Update 2 of the Data Synchronizer Mobility Pack provides the following enhanced features:
Synchronizer System Update: When you update the Mobility Pack software, you also update
the Mobility database, so that all device information is retained during the update process.
GroupWise Authentication: You can configure the Mobility Connector to accept GroupWise
mailbox passwords instead of LDAP (network) passwords when mobile devices connect to the
Synchronizer system.
GroupWise Connector Monitoring: Synchronizer Web Admin now provides a Connector
Information Monitoring page for the GroupWise Connector, similar to what was already
available for the Mobility Connector.
Improved Device Blocking: The Mobility Connector Information Monitoring page displays
the traffic level for each mobile device. This assists in recognizing when a device needs to be
blocked because it is having synchronization problems. This prevents a synchronization issue
with one device from impacting performance for all other devices.
Synchronization of Attachments: When an attachment is too large to synchronize to your
mobile device, the item still includes the attachment icon and indicates that the attachment was
not downloaded because of its size.
Synchronization of Notes: You can synchronize reminder notes, discussion notes, or both.
Nightly Maintenance: Items in the Mobility database that have exceeded the age limit for
retention on mobile devices are automatically cleared from the database to maintain optimum
database performance.
For a list of the bugs that have been fixed since Update 1 of the Data Synchronizer Mobility Pack,
see Section 9, “Mobility Pack Update 2 Bug Fixes,” on page 16.
2 System Requirements
See “Data Synchronizer System Requirements” in the Novell Data Synchronizer Mobility Pack
Installation Guide.
3 Mobility Pack Update Instructions
Follow the instructions in this section to update an existing Synchronizer system.
Novell Data Synchronizer Mobility Pack Update 21
If you are installing Novell Data Synchronizer Mobility Pack Update 2 as your initial Synchronizer
system, see Section 4, “Mobility Pack Installation Instructions,” on page 5.
Updates for the Data Synchronizer Mobility Pack software are released regularly. You can update
the Mobility Pack software while retaining the configuration of your existing Synchronizer system,
including commercially signed certificates that you have purchased.
If you update from the Novell Customer Center, you can subscribe to receive future updates through
the Novell Update channel. Or, if you update from the Novell Download Web site, you must
periodically check for future updates.
Section 3.1, “Updating from the Novell Customer Center,” on page 3
Section 3.2, “Updating from the Novell Downloads Web Site,” on page 4
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.7, “Thorough Uninstallation Required,” on page 10.
3.1 Updating from the Novell Customer Center
When you update the Mobility Pack software from the Novell Customer Center, you automatically
obtain the software through the Novell Update channel. This is a convenient way to receive regular
updates.
1 Log in to the Novell Customer Center (http://www.novell.com/customercenter).
2 (Conditional) If you have not already done so, obtain the product registration code for the Data
Synchronizer Mobility Pack and register to receive Mobility Pack updates.
Data Synchronizer Mobility Pack Update 2 is then delivered through the Novell Update
channel to your Synchronizer server.
3 Apply Data Synchronizer Mobility Pack Update 2 to the Synchronizer server:
zypper up -r nu_novell_com:Mobility-1.0-Updates
4 Run the Update script to update the Synchronizer database (
database (
/opt/novell/datasync/update.sh
mobility
) for use with the updated software:
datasync
) and the Mobility
5 Restart the Synchronizer services.
6 Verify that Update 2 has been applied:
cat /opt/novell/datasync/version
The version number in the
version
file should match the version number in the filename of the
ISO from which you installed Update 2. For convenience, this version number is also displayed
in Synchronizer Web Admin.
For more detailed instructions, see “Updating from the Novell Customer Center” in “Mobility Pack
Installation” in the Novell Data Synchronizer Mobility Pack Installation Guide.
2Novell Data Synchronizer Mobility Pack Update 2
3.2 Updating from the Novell Downloads Web Site
When you update the Mobility Pack software from the Novell Downloads Web site, you manually
download and install the software whenever you choose.
1 Download the Novell Data Synchronizer Mobility Pack Update 2 ISO file from Novell
Downloads (http://download.novell.com) to a convenient temporary directory on the
Synchronizer server.
IMPORTANT: The Mobility Pack Update 2 software is located on the Patches list, not the
Products list.
2 Use YaST to update the Mobility Pack repository from the new ISO file:
2a Under Groups, click Software, then click Patch CD Update.
2b Follow the prompts to install the updated software from the ISO file.
3 Run the Update script to update the Synchronizer database (
database (
/opt/novell/datasync/update.sh
4 Restart the Synchronizer services.
5 Verify that Update 2 has been applied:
cat /opt/novell/datasync/version
The version number in the
ISO from which you installed Update 2. For convenience, this version number is also displayed
in Synchronizer Web Admin.
6 Check the Novell Downloads Web site periodically for updates.
mobility
) for use with the updated software:
version
file should match the version number in the filename of the
datasync
) and the Mobility
For more detailed instructions, see “Updating from the Novell Downloads Web Site” in “Mobility
Pack Installation” in the Novell Data Synchronizer Mobility Pack Installation Guide
4 Mobility Pack Installation Instructions
Follow the instructions in this section if you are installing Novell Data Synchronizer Mobility Pack
Update 2 in order to create your initial Synchronizer system. The Update 2 software is available on
the Novell Downloads Web site.
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.7, “Thorough Uninstallation Required,” on page 10.
1 Make sure that the Linux server where you plan to install the Mobility Pack meets the system
requirements.
For system requirements, see “Data Synchronizer System Requirements” in the Novell Data
Synchronizer Mobility Pack Installation Guide.
For additional planning assistance, see the Data Synchronizer Mobility Pack Best Practices
Wiki (http://wiki.novell.com/index.php/Data_Synchronizer_Mobility_Pack_Best_Practices).
2 If a Web server is currently running on the Synchronizer server, stop it, and preferably disable
it.
Novell Data Synchronizer Mobility Pack Update 23
3 Download the Novell Data Synchronizer Mobility Pack ISO file to a convenient temporary
directory:
3a On the Novell Downloads Web site (http://download.novell.com), click Search Patches in
the Patches box.
3b In the Standard Select field, select Data Synchronizer.
IMPORTANT: If you do not see Data Synchronizer, you are looking in the Product list,
not the Patch Finder list. Click Search Patches to the right of the Product list, then look in
the Patch Finder list.
3c Under Current Patches, click the Novell Data Synchronizer Mobility Pack Update 2 x86-
64 link to display information about the download.
3d Review the description of Update 2, then click Proceed to Download.
3e Follow the online instructions to download the Update 2 ISO file to a convenient location.
4 Use YaST to install the Data Synchronizer Mobility Pack software:
4a Under Groups, click Software, then click Add-On Products.
4b Install the Data Synchronizer 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.
After you have installed Update 2, you can register in the Novell Customer Center to receive future
updates through the Novell Update channel, as described in “Updating from the Novell Customer
Center” in “Mobility Pack Installation” in the Novell Data Synchronizer Mobility Pack Installation
Guide.
5 Installation Issues
Section 5.1, “GroupWise Trusted Application Creation,” on page 8
Section 5.2, “YaST Proposal Error,” on page 8
Section 5.3, “YaST Hangs When Browsing Files in the Installation Program,” on page 8
Section 5.4, “Required Python Package Version,” on page 9
Section 5.5, “Mobility Pack Installation Program Fails on a 32-Bit/x86 Processor,” on page 9
Section 5.6, “Overhead of Extraneous Users,” on page 9
Section 5.7, “Thorough Uninstallation Required,” on page 10
5.1 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 only need to fill in 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.
4Novell Data Synchronizer Mobility Pack Update 2
5.2 YaST Proposal Error
When you run the Data Synchronizer 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.3 YaST Hangs When Browsing Files in the Installation
Program
When you run the Data Synchronizer Mobility Pack Installation program on SLES 11 SP1, if you
browse to and select a file, the Installation program might hang. This can occur if you try to browse
to and select any of the following files during installation:
As a workaround, type the full path and filename for the file instead of browsing to it.
5.4 Required Python Package Version
If you already have Python packages installed on the server where you are installing the Data
Synchronizer Mobility Pack, the Data Synchronizer Mobility Pack Installation program needs to
update the existing packages, rather than install new packages. This does not happen by default.
1
When you run the Installation program, you are prompted if packages need to be updated. Enter
Solution 1
for
to update each package.
5.5 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 Mobility Pack 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.
Novell Data Synchronizer Mobility Pack Update 25
5.6 Overhead of Extraneous Users
When you add users to your Synchronizer system, data is automatically synchronized from
GroupWise to the GroupWise 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.7 Thorough Uninstallation Required
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 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.
In YaST, click Software > Software Management. In the Filters drop-down list, select Patterns.
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.
In YaST, click Software > Software Management. In the Search field, specify
datasync
, then
click Search. The Packages list should be empty. If any Data Synchronizer packages are still
listed, uninstall them.
Log in as
rpm -qa | grep datasync
root
in a terminal window, then check for Data Synchronizer RPMs:
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:
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 Tools > Options > Advanced > Encryption > View
Certificates. Select the certificate named
DataSync Web Admin
, then click Delete.
6Novell Data Synchronizer Mobility Pack Update 2
6 Data Synchronizer Issues
Section 6.1, “Sync Engine Restart Stops All Connectors,” on page 12
Section 6.2, “Users and Groups Not Displayed Correctly in Synchronizer Web Admin,” on
page 12
Section 6.3, “Synchronizer Web Admin Responsiveness,” on page 12
Section 6.4, “Illegal Server Error in Synchronizer Web Admin,” on page 12
Section 6.5, “Connector Configuration Settings,” on page 13
Section 6.6, “Internet Explorer 8 Compatibility,” on page 13
Section 6.7, “GroupWise Mobile Server Compatibility,” on page 13
6.1 Sync Engine Restart Stops All Connectors
When the Sync Engine is stopped or restarted, it forces all connectors to stop. After the Sync Engine
is restarted, restart the Connector Manager service. After the Connector Manager service is
restarted, restart each connector in Synchronizer Web Admin or configure the connectors to start
automatically.
6.2 Users and Groups Not Displayed Correctly in Synchronizer
Web Admin
When you add or delete a large number of users or groups, 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 Synchronizer Web Admin Responsiveness
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.
6.4 Illegal Server Error in Synchronizer Web Admin
You might occasionally see an Illegal Server Error when you log in to Synchronizer Web Admin
immediately after stopping and starting the Synchronizer services and connectors. This occurs if the
GroupWise Connector is not completely started when you access Synchronizer Web Admin. The
GroupWise Connector must process any accumulated events before it is ready to provide connector
status information to Synchronizer Web Admin. After the GroupWise Connector is completely
started, the Illegal Server Error no longer occurs.
Novell Data Synchronizer Mobility Pack Update 27
6.5 Connector Configuration Settings
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.
6.6 Internet Explorer 8 Compatibility
If you use Synchronizer Web Admin on Internet Explorer 8, you must enable Compatibility View in
order to display the Sync Engine Advanced options on the Engine Settings page.
1 In Internet Explorer 8, click Tools, then select Compatibility View.
Even with Compatibility View enabled, the Maintenance section on the Engine Settings page
sometimes disappears when you mouse over it. However, with persistent mousing, it is still possible
to click Clear Cache.
6.7 GroupWise Mobile Server Compatibility
Novell Data Synchronizer 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 Connector Issues
Section 7.1, “General Connector Issues,” on page 14
Section 7.2, “Connector-Specific Issues,” on page 15
7.1 General Connector Issues
“User Deletion” on page 14
“Connector Does Not Stop” on page 14
“Multiple Instances of the Same Connector” on page 15
7.1.1 User Deletion
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.
8Novell Data Synchronizer Mobility Pack Update 2
7.1.2 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:
1 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.
2 Start the connector in Synchronizer Web Admin.
3 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.
7.1.3 Multiple Instances of the Same Connector
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 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.
7.2 Connector-Specific Issues
Refer to the Readme for each connector on the Novell Data Synchronizer Connectors
Documentation Web site (http://www.novell.com/documentation/datasync_connectors1).
8 GroupWise 8.0.2 Issues
The Mobility Pack depends on the GroupWise Connector and a GroupWise POA for much of its
functionality. GroupWise 8.0.2 is required for use with the Mobility Pack. However, GroupWise
8.0.2 was released with some issues that impact Mobility Pack functionality. Fixes for these issues
will be available in an upcoming GroupWise 8.0.2 hot patch. For a list of GroupWise 8.0.2 issues,
see the GroupWise Connector Readme for Data Synchronizer Mobility Pack Update 2 (http://
For a list of the bugs that have been fixed in Novell Data Synchronizer Mobility Pack Update 2, see
the Novell Data Synchronizer Mobility Pack Update 2 Bug Fix List (http://www.novell.com/
In addition to the Data Synchronizer product documentation, the following resources provide
additional information about Data Synchronizer:
Novell Support and Knowledgebase (http://www.novell.com/support)
Data Synchronizer Support Forum (http://forums.novell.com/novell-product-support-forums/
data-synchronizer)
Data Synchronization Cool Solutions (http://www.novell.com/communities/coolsolutions/
datasynchronizer)
Data Synchronizer Mobility Pack Best Practices Wiki (http://wiki.novell.com/index.php/
Data_Synchronizer_Mobility_Pack_Best_Practices)
Data Synchronizer Mobility Connector Wiki (http://wiki.novell.com/index.php/
Data_Synchronizer_Mobility_Connector)
11 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.
10Novell Data Synchronizer Mobility Pack Update 2
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 (http://www.novell.com/info/exports/) for
more information on exporting Novell software. Novell assumes no responsibility for your failure to
obtain any necessary export approvals.