June 2, 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.1.2 provides the following enhanced features compared to Mobility Pack 1.1.1:
More Secure Synchronizer Web Admin URL: Log in to Synchronizer Web Admin using the following URL:
https://data_synchronizer_server:8120/login
Replace data_synchronizer_server with the IP address or DNS hostname of the server where you installed the Mobility Pack.
Performance and Stability Improvements: Synchronization occurs more rapidly and consistently.
Calendar Improvements: Calendar synchronization is more reliable.
Attachment Improvements: Attachment synchronization is more reliable.
Database Cleanup Improvements: Synchronizer database cleanup is more thorough and reliable.
Reply/Forward Icons: If you reply to or forward an item on your mobile device, the typical or icon now displays when you view the item in a GroupWise client.
Updates to the Mobility Pack are released regularly. Some updates are major version updates, such as Mobility Pack 1 to Mobility Pack 1.1, where a new ISO file is required. Other updates are minor updates, such as Mobility Pack 1.1 to Mobility Pack 1.1.x, where updated RPMs can be automatically received through the Novell Update channel or a new ISO file can be obtained.
For a list of the bugs that have been fixed since Mobility Pack 1.1.1, see the Novell Data Synchronizer Mobility Pack 1.1.2 Bug Fix List.
See Data Synchronizer System Requirements
in the Novell Data Synchronizer Mobility Pack Installation Guide.
Follow the instructions in this section if you are installing Mobility Pack 1.1.2 in order to create a new Synchronizer system. You can create a new Synchronizer system using software that is either a major update or a minor update to the Synchronizer software.
The Mobility Pack 1.1.2 ISO is available from the Novell Downloads Web site. You use YaST to install Mobility Pack 1.1.2 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.9, Thorough Uninstallation Required.
On Novell Downloads, click .
IMPORTANT:The Mobility Pack 1.1.2 software is located in the list, not the list.
Select , then click .
Under , click .
Click , then follow the online instructions to download the Mobility Pack 1.1.2 ISO to a convenient temporary directory on the Synchronizer server.
Continue with Installing Mobility Pack 1.1.2 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.1.2 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 when you install either a major update or a minor update.
You can use this update procedure to install either a major update or a minor update.
Obtain the Mobility Pack 1.1 ISO from the Novell Customer Center.
or
Obtain the Mobility Pack 1.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.
Run the Mobility Pack Update script.:
/opt/novell/datasync/update.sh
Restart the Synchronizer services.:
rcdatasync restart
For more detailed instructions, see Updating to the Next Major Version (Mobility Pack 1 to Mobility Pack 1.1)
in Novell Data Synchronizer Mobility Pack Installation Guide.
You can use this update procedure to install a minor update, or you can install a minor update using the procedure described in Section 4.1, Using Patch CD Update in YaST to Install a Mobility Pack Update.
(Conditional) If you have not already done so, obtain the Mobility Pack activation code from the Novell Customer Center.
(Conditional) If you have not already done so, register to receive Mobility Pack updates through the Novell Update channel:
suse_register -a regcode-mobility=registration_code -a email=email_address -L /root/.suse_register.log
Replace registration_code with the Mobility Pack activation code that you obtained from the Novell Customer Center. Replace email_address with the e-mail address that you used to log in to the Novell Customer Center. Notifications about future Mobility Pack updates will be sent to this e-mail address.
When you receive a notification about a minor update, apply the update to the Synchronizer server:
zypper up -r nu_novell_com:Mobility-1.1-Updates
This command updates your Synchronizer system to the next minor update of the Mobility Pack software through the Novell Update Channel.
Run the Mobility Pack Update script:
/opt/novell/datasync/update.sh
Restart the Synchronizer services:
rcdatasync restart
For more detailed instructions, see Updating to the Next Minor Version (Mobility Pack 1.1.x)
in Novell Data Synchronizer Mobility Pack Installation Guide.
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 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 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.
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 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.
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 . 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 the heading, 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 . In the field, specify datasync, then click . The list 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 . Select the certificate named DataSync Web Admin, then click .
GroupWise authentication is slower than LDAP authentication. To prevent users from experiencing slower synchronization because of the authentication process, GroupWise authentication now includes session caching. Login requests occur regularly every 15 minutes instead of every time mobile devices connect to synchronize. As a result, users are already authenticated whenever synchronization needs to occur.
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 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.
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.
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.
If you use Synchronizer Web Admin on Internet Explorer 8 or 9, you must enable Compatibility View in order to display the Sync Engine options on the Engine Settings page.
In Internet Explorer 8 or 9, click , then select .
Even with Compatibility View enabled, the section on the Engine Settings page sometimes disappears when you mouse over it. However, with persistent mousing, it is still possible to click .
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:
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 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.
When you add a new user to a connector, you must click on the Add User to Connector page and immediately set the application username for the new user. If you click without setting the application username, the translation of displays in the column for the new user and cannot be reset at that point.
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. For a list of GroupWise 8.0.2 issues, see the GroupWise Connector Readme.
IMPORTANT:GroupWise 8.0.2 Hot Patch 2 resolves all of these GroupWise 8.0.2 issues.
For a list of the bugs that have been fixed since Mobility Pack 1.1.1, see the Novell Data Synchronizer Mobility Pack 1.1.2 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 Administration Guide
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-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.