October 12, 2010
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.
For information about specific mobile devices, see the Novell Data Synchronizer Mobility Connector Wiki.
For a list of the bugs that have been fixed since the original release of the Data Synchronizer Mobility Pack, see Section 9.0, Mobility Pack Update 1 Bug Fixes.
See Data Synchronizer System Requirements
in the Novell Data Synchronizer Mobility Pack Installation Guide.
If you are installing Novell Data Synchronizer Mobility Pack Update 1 as your initial Synchronizer system, see Section 4.0, Mobility Pack Installation Instructions.
Follow the instructions in this section to update an existing Synchronizer system. 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.
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.8, Thorough Uninstallation Required.
Log in to the Novell Customer Center.
Obtain the product registration code for the Data Synchronizer Mobility Pack:
In the
drop-down list, select your organization that is entitled to the Novell Data Synchronizer Mobility Pack.Under
, select .Make a note of the numbers and letters in the
field.Register to receive Mobility Pack updates:
In a terminal window on the Synchronizer server, enter the following command:
suse_register -a regcode-mobility=registration_code -a email=email_address -L /root/.suse_register.log
Replace registration_code with the Mobility Pack registration code that you obtained from the Novell Customer Center in Step 2. Replace email_address with the e-mail address where you want Mobility Pack update notifications to be sent for future updates.
Enter the following command to verify that the Novell Update channels for the Mobility Pack have been added on your Synchronizer server:
zypper ca
This command lists all channels where you are registered to receive updates. The following Mobility Pack update channels should be listed:
Apply Data Synchronizer Mobility Pack Update 1 to the Synchronizer server:
Enter the following command:
zypper up -r nu_novell_com:Mobility-1.0-Updates
Seven Mobility Pack packages are listed for update through the channel for Update 1.
Enter YES to start the update process.
Restart the Synchronizer services:
Stop the Synchronizer services:
rcdatsync stop
Verify that all Synchronizer services have stopped:
ps -eaf | grep datasync
Start the Synchronizer services:
rcdatsync start
Repeat Step 4 and Step 5 each time you receive a notification that a Mobility Pack update is available.
Download the Novell Data Synchronizer Mobility Pack ISO file from Novell Downloads to a convenient temporary directory on the Synchronizer server:
On the Novell Downloads Web site, click
in the gray Patches box on the right.In the
field, select .IMPORTANT:If you do not see
, you are looking in the list, not the list. Click to the right of the list, then look in the list.Under
, click the link to display information about the download.Review the description of Update 1, then click
.Follow the online instructions to download the Update 1 ISO file to a convenient location.
Use YaST to update the Mobility Pack repository from the new ISO file:
Under
, click , then click .Click
to start the update.Select
, then click .In the
field, specify a name for the repository for the Mobility Pack Update 1 software.In the
field, specify the full pathname to the Mobility Pack Update 1 ISO file, then click .Click
to accept the License Agreement, then click .On the Distribution Upgrade Settings page, click
.In the Confirm Update dialog box, click
.On the Novell Customer Center Configuration page, select
, then click .(Conditional) If you receive a warning that no changes were made to the list of registered repositories and offering to let you rerun the registration, click
.On the Migration Completed page, click
.Restart the Synchronizer services:
Stop the Synchronizer services:
rcdatsync stop
Verify that all Synchronizer services have stopped:
ps -eaf | grep datasync
Start the Synchronizer services:
rcdatsync start
Check the Novell Downloads Web site periodically for updates.
At any time after your initial installation of the Mobility Pack, you can register to receive automatic notifications when updates are available, as described in Section 4.2, Registering to Receive Future Updates through the Novell Update Channel (Optional).
Follow the instructions in this section if you are installing Novell Data Synchronizer Mobility Pack Update 1 in order to create your initial Synchronizer system. The Update 1 software is available on the Novell Downloads Web site.
After you have installed Update 1, you can register in the Novell Customer Center to receive future updates through the Novell Update channel.
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.8, Thorough Uninstallation Required.
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.
If a Web server is currently running on the Synchronizer server, stop it, and preferably disable it.
Download the Novell Data Synchronizer Mobility Pack ISO file to a convenient temporary directory:
On the Novell Downloads Web site, click in the Patches box.
In the
field, select .IMPORTANT:If you do not see
, you are looking in the list, not the list. Click to the right of the list, then look in the list.Under
, click the link to display information about the download.Review the description of Update 1, then click
.Follow the online instructions to download the Update 1 ISO file to a convenient location.
Use YaST to install the Data Synchronizer Mobility Pack software:
Under
, click , then click .Install the Data Synchronizer Mobility Pack as an add-on product.
Complete installation instructions are available in the Novell Data Synchronizer Mobility Pack Installation Guide.
After you have installed Mobility Pack Update 1 to create your initial Synchronizer system, you can register to receive future updates through the Novell Update channel, as described in Section 3.1, Updating from the Novell Customer Center:
To register for future updates, complete Step 1 through Step 3 in Section 3.1, Updating from the Novell Customer Center.
After you receive notification of the next Mobility Pack update, complete Step 4 and Step 5 in Section 3.1, Updating from the Novell Customer Center
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: , , 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 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
without 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 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:
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.
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.
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 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.
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.
Use only alphanumeric characters in the Synchronizer database password. Do not include special characters. The Sync Engine does not start if the database password includes special characters.
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 .
. TheIMPORTANT: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, specifyLog 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 namedIf the LDAP server is restarted while Synchronizer is running, Synchronizer loses its connection to the LDAP server. Occasionally, the connection to the LDAP server is lost for other reasons. To reestablish the connection, restart the Synchronizer services.
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.
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.
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.
If a user’s LDAP username includes a space, the user cannot log in to the Data Synchronizer User Options page.
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.
In Internet Explorer 8, click
, then select .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
.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.
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 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:
rcdatasync-connectors restart
This should change the connector status in Synchronizer Web Admin from
to .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 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.
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 as hot patches or in the next GroupWise release. For a list of GroupWise 8.0.2 issues, see the GroupWise Connector Readme.
The following bugs have been fixed in Update 1 of the Mobility Pack:
Synchronization performance has been substantially improved.
638990: After initial synchronization, new items promptly synchronize from GroupWise to mobile devices.
633751: Time stamps are correctly set on mobile devices.
601547: Work ZIP codes are synchronized for contacts.
632889: Contacts with categories are not duplicated on mobile devices.
633839: Appointments that lack a time zone setting are successfully synchronized to mobile devices.
640646: When you modify an appointment in GroupWise, the change synchronizes successfully to your mobile device when your device is configured to handle conflict detection.
You can look up the bug numbers in Bugzilla for more information about each bug.
Novell Data Synchronizer Mobility Pack documentation is available at the Novell Data Synchronizer Documentation Web site:
Novell Data Synchronizer Mobility Pack Readme
Novell Data Synchronizer installation and administration guides
Novell Data Synchronizer connector documentation is available at the Novell Data Synchronizer Connector Documentation Web site
Connector Readmes
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 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.