novdocx (en) 16 April 2010
Novell Data Synchronizer Mobility Pack

Readme

Novell

September 10, 2010

1 Overview
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 (http://wiki.novell.com/index.php/Data_Synchronizer_Mobility_Connector).

2 System Requirements

System requirements are listed in the Novell Data Synchronizer Mobility Pack Installation Guide (http://www.novell.com/documentation/datasynchronizer1).
3 Mobility Pack Installation Instructions
1 Make sure that the Linux server where you plan to install the Mobility Pack meets the system requirements. 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. 3 Download the Novell Data Synchronizer Mobility Pack ISO file from Novell Downloads (http://download.novell.com) to a convenient temporary directory:
novell-data-synchronizer-mobility-pack-x86_64-build_number.iso
4 On your Linux desktop, click Computer > YaST, then enter the root password. 5 Under Groups, click Software, then click Add-On Products. 6 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 (http://www.novell.com/documentation/datasynchronizer1). NOTE: If you need to uninstall and reinstall the Mobility Pack, follow the instructions in Uninstalling the Mobility Pack in the Novell Data Synchronizer Installation Guide (http:// www.novell.com/documentation/datasynchronizer1). See also Section 4.8, Thorough Uninstallation Required, on page 3

4 Installation Issues

Section 4.1, GroupWise Trusted Application Creation, on page 2 Section 4.2, YaST Proposal Error, on page 2 Section 4.3, YaST Hangs When Browsing Files in the Installation Program, on page 2 Section 4.4, Required Python Package Version, on page 3 Section 4.5, Mobility Pack Installation Program Fails on a 32-Bit/x86 Processor, on page 3 Section 4.6, Overhead of Extraneous Users, on page 3 Section 4.7, Database Password Restriction, on page 3 Section 4.8, Thorough Uninstallation Required, on page 3
4.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.

4.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.
4.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: 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.
4.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. When you run the Installation program, you are prompted if packages need to be updated. Enter 1 for Solution 1 to update each package.
4.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 (http://www.novell.com/ documentation/datasynchronizer1), 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.

4.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.
4.7 Database Password Restriction
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.
4.8 Thorough Uninstallation Required
The standard uninstallation procedures provided in Uninstalling the Mobility Pack in the Novell Data Synchronizer Mobility Pack Installation Guide (http://www.novell.com/documentation/ datasynchronizer1) 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 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 Tools > Options > Advanced > Encryption > View Certificates. Select the certificate named DataSync Web Admin, then click Delete.
5 Data Synchronizer Issues
Section 5.1, LDAP Server Restart Issue, on page 4 Section 5.2, Sync Engine Restart Stops All Connectors, on page 5 Section 5.3, Users and Groups Not Displayed Correctly in Synchronizer Web Admin, on page 5 Section 5.4, Synchronizer Web Admin Responsiveness, on page 5 Section 5.5, Usernames with Spaces, on page 5 Section 5.6, Internet Explorer 8 Compatibility, on page 5 Section 5.7, GroupWise Mobile Server Compatibility, on page 5
5.1 LDAP Server Restart Issue
If 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.
5.2 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.
5.3 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.
5.4 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.
5.5 Usernames with Spaces
If a users LDAP username includes a space, the user cannot log in to the Data Synchronizer User Options page.
5.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.
5.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.

6 Connector Issues

Section 6.1, General Connector Issues, on page 6 Section 6.2, Connector-Specific Issues, on page 7
6.1 General Connector Issues
User Deletion on page 6 Connector Does Not Stop on page 6 Multiple Instances of the Same Connector on page 6 6.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. 6.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. 6.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.
6.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).

7 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 as hot patches or in the next GroupWise release. For a list of GroupWise 8.0.2 issues, see the GroupWise Connector Readme (http://www.novell.com/documentation/ datasync_connectors1).

8 Documentation

Novell Data Synchronizer Mobility Pack documentation is available at the Novell Data Synchronizer Documentation Web site (http://www.novell.com/documentation/datasynchronizer1): 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 (http://www.novell.com/documentation/datasync_connectors1) 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 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)

9 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 (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. 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 (http://www.novell.com/ company/legal/trademarks/tmlist.html). All third-party trademarks are the property of their respective owners.

Section 1.1.1, Data Synchronizer Capabilities, on page 9 Section 1.1.2, Data Synchronizer Components, on page 10 Section 1.1.3, Data Synchronizer Configurations, on page 13
1.1.1 Data Synchronizer Capabilities
The Data Synchronizer Mobility Pack installs a Synchronizer system, the GroupWise Connector, and the Mobility Connector. This configuration is the next generation of mobile device support for GroupWise users. Many popular mobile device operating systems are supported, including Android, Apple, Maemo, Palm, Symbian, and Windows Mobile.
GroupWise GroupWise Connector Microsoft Sharepoint Mobile Devices Mobility Connector

SharePoint Connector

Salesforce.com Connector

Data Synchronizer

SugarCRM Connector

Future Connectors

salesforce.com

SUGARCRM

Salesforce.com

Sugar CRM

More Applications Supported Soon!
For information about other connectors, visit the Data Synchronizer Connector Marketplace (http:// www.novell.com/products/data-synchronizer/connectors). After you have created your Synchronizer system by installing the Mobility Pack, you can add additional connectors to synchronize GroupWise data with other supported applications, as described in Connectors on page 11.
1.1.2 Data Synchronizer Components
A Synchronizer system consists of several components that are installed together on one server when you install the Data Synchronizer Mobility Pack.
Synchronization Engine on page 11 Web Administration Service on page 11 Configuration Engine on page 11 Connector Manager on page 11 Connectors on page 11
Synchronizer Web Admin Web Admin Service
Synchronizer Server Connector Connector

Web Browser

Config Engine Connector Manager Sync Engine
Synchronization Engine The Synchronizer Sync Engine (datasync-syncengine) is a service that provides the hub of data flow between one or more pairs of application-specific connectors. The Sync Engine provides the common ground among various applications, so that data provided to the Sync Engine from one application through its connector can be passed to one or more different applications through their connectors. Web Administration Service The Synchronizer Web Administration service (datasync-webadmin) provides a Web-based interface called Synchronizer Web Admin for administration and management of your Synchronizer system. Synchronizer Web Admin allows you to add and remove connectors, as well add or remove users for specific connectors and configure their individual synchronization settings. Users can log in to the Synchronizer Web Admin URL using their personal network login credentials to access the Data Synchronizer User Options page. Here, they can configure and control the synchronization settings for their applications. For more information, see the Quick Start (http:// www.novell.com/documentation/datasync_connectors1) for each connector. Configuration Engine The Synchronizer Config Engine (datasync-configengine) is a service that provides communication between Synchronizer Web Admin and the Sync Engine. The Config Engine passes configuration information from the Sync Engine to Synchronizer Web Admin for viewing, and it passes your configuration changes back to the Sync Engine for implementation. Connector Manager The Synchronizer Connector Manager (datasync-connectors) is a service that provides communication between the Sync Engine and connectors. Connectors Synchronizer Connectors transfer data between two or more applications. Each connector acts as a code converter and data filter to translate information between an application-specific format and an application-neutral format that can be consumed by other application-specific connectors. For

Static IP address SUSE Linux Enterprise Server (SLES) 11, plus the latest Support Pack PostgreSQL
If PostgreSQL is not already installed on the Synchronizer server, the Mobility Pack Installation program installs it for you.
Time synchronization among servers
For the most reliable synchronization of time-sensitive items such as appointments, the Synchronizer server and GroupWise servers should have their time synchronized as closely as possible. This is especially important on virtual machines.
1.2.2 Directory Service Requirement
Lightweight Directory Access Protocol (LDAP) v3
1.2.3 Web Browser Requirements for Synchronizer Web Admin
Any of the following Web browsers:
Mozilla FireFox 3 or later Microsoft Internet Explorer 7 or 8 Safari 3
1.2.4 Connector Requirements
The system requirements for each Synchronizer connector are listed in the Installation and Configuration Guide (http://www.novell.com/documentation/datasync_connectors1) for each connector.
Mobility Pack Installation
The Data Synchronizer Mobility Pack Installation program available in YaST helps you install the Data Synchronizer services, the GroupWise Connector, and the Mobility Connector to set up your initial Synchronizer system.
Section 2.1, Planning a Data Synchronizer System, on page 17 Section 2.2, Preparing to Install the Mobility Pack Software, on page 28 Section 2.3, Installing and Setting Up a Data Synchronizer System, on page 30 Section 2.4, Whats Next, on page 37 Section 2.5, Mobility Pack Installation Summary Sheet, on page 39
2.1 Planning a Data Synchronizer System
You can use the Mobility Pack Installation Summary Sheet on page 39 to gather the information you need so that you are prepared to provide the information requested by the Mobility Pack Installation program. The Summary Sheet organizes the information in the order in which you need it during the installation and configuration process.
Section 2.1.1, Planning Your Data Synchronizer System Configuration, on page 17 Section 2.1.2, Gathering LDAP Information, on page 18 Section 2.1.3, Planning How to Add Users, on page 20 Section 2.1.4, Gathering GroupWise System Information, on page 22 Section 2.1.5, Gathering Mobile Device Information, on page 25 Section 2.1.6, Planning the Data Synchronizer Database, on page 26 Section 2.1.7, Establishing Data Synchronizer System Security, on page 27 Section 2.1.8, Registering for Automatic Updates from the Novell Customer Center (in
Mobility Pack 1.1.1 or later), on page 27 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).

regularly, which requires reconfiguration of mobile devices each time the LDAP passwords expire. GroupWise passwords do not expire. Device reconfiguration becomes necessary only when users manually change their own GroupWise passwords.
Under Enable GroupWise Authentication?, mark Yes if you plan to reconfigure the Mobility Connector to use GroupWise passwords to authenticate to mailboxes.
After you have installed the Mobility Pack, enable GroupWise authentication by following the instructions in Using GroupWise Authentication Instead of LDAP Authentication for Mobile Devices in Mobility Connector Configuration in the Mobility Connector Installation and Configuration Guide.
2.1.3 Planning How to Add Users
If you plan to use LDAP authentication, a number of variables affect how you add users to your Synchronizer system:
During installation During installation, you can add individual users and groups of users to your Synchronizer system from any context in your LDAP directory where the LDAP administrator user has rights to access the User and Group objects. For a small Synchronizer system, you might plan to add all users during installation. When you add users during installation, the following GroupWise data is automatically synchronized for each user:
Contacts from all personal address books, excluding the Frequent Contacts address
Calendar items (appointments and reminder notes) from the last two weeks and all

future items

E-mail messages in the Mailbox folder from the last three days Standard folders (Sent Items, Work in Progress, Junk Mail, and Trash) and folders
in the Cabinet (but not the items in the folders until users request them by opening folders) Adding at least two users for testing purposes during installation is recommended. After installation For a larger Synchronizer system, you might plan to add a subset of users during installation, get those users running smoothly, then add the rest of the users after installation using Synchronizer Web Admin. If you want to restrict the amount of data that is processed during initial synchronization, add the users after you have installed the Mobility Pack. Configure the GroupWise Connector to meet your synchronization preferences, as described in GroupWise Connector Configuration in the Groupwise Connector Installation and Configuration Guide, then add the users manually, as described in Managing Users in Managing Connectors and Users in the Novell Data Synchronizer System Administration Guide.

Using LDAP groups

The Mobility Pack Installation program lets you select individual users or LDAP groups of users to add to your Synchronizer system. You might already have existing LDAP groups that represent useful sets of users to add to your Synchronizer system. If your existing LDAP groups do not meet the needs of your Synchronizer system, you can organize your users into LDAP groups specifically to facilitate the Mobility Pack installation and the post-installation growth of your Synchronizer system. LDAP groups are a powerful tool for ongoing Synchronizer system management. When you add LDAP groups to your Synchronizer system, you can later add and delete users in the LDAP groups, and the users are automatically added or deleted for all connectors that are configured with those groups. This saves you from the repetitive work of manually adding or deleting users for two or more connectors using Synchronizer Web Admin. When you add or delete the users in the LDAP group, Synchronizer Web Admin automatically adds or deletes the users for all connectors that are configured with the group. LDAP groups also make the installation process more convenient. The YaST functionality of the Mobility Pack Installation program does not allow for Ctrl+click to select multiple users. It is much easier to add multiple users to an LDAP group than it is to select them individually in the Mobility Pack Installation program. IMPORTANT: LDAP groups must include at least one user in order to be added to your Synchronizer system during installation.

GroupWise Trusted Application on page 22 GroupWise Post Office Agent on page 23 GroupWise Address Book User on page 24
GroupWise Trusted Application A GroupWise trusted application can log into a GroupWise Post Office Agent (POA) in order to access GroupWise mailboxes without needing personal user passwords. The GroupWise Connector requires such mailbox access in order to synchronize GroupWise data with mobile devices and with other applications. In addition, the Mobility Connector uses trusted application authentication through the GroupWise Connector in order to access the GroupWise Address Book to provide contact lookup beyond the contacts that are downloaded to users devices from personal address books. Before you install the Mobility Pack, you must use ConsoleOne to configure the GroupWise Connector as a GroupWise trusted application. You might name the trusted application MobilityPack or GroupWiseConnector. A trusted application uses a key that consists of a long string of letters and numbers to provide authentication to the GroupWise POA. ConsoleOne creates the key in a file in a specified location that is accessible to ConsoleOne. You need to create only one trusted application key for the GroupWise Connector, regardless of the number of servers where you install the Mobility Pack, and regardless of the number of domains and post offices in your GroupWise system. NOTE: If your GroupWise system connects to any external GroupWise domains, that external GroupWise system needs its own Mobility Pack installation on an additional Synchronizer server, along with its own separate trusted application key.
Follow the instructions in Creating a Trusted Application and Key in System in the GroupWise 8 Administration Guide to set up a trusted application and obtain a trusted application key for the GroupWise Connector. IMPORTANT: Do not use an existing trusted application key that is already in use by another application. 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 Name of Key File
Do not fill in any other fields. IMPORTANT: In order for the Mobility Pack Installation program to access the key file, you might need to copy it to a convenient location on the Synchronizer server. The Installation program automatically transfers the trusted application key from the key file into the configuration of the GroupWise Connector.
Under GroupWise Trusted Application, specify the name of the trusted application that you created in ConsoleOne and the location where the Mobility Pack Installation program can access the trusted application key file.
GroupWise Post Office Agent The GroupWise Connector accesses your GroupWise system by communicating with a Post Office Agent (POA). The selected POA must be configured for SOAP, as described in Supporting SOAP Clients in Post Office Agent in the GroupWise 8 Administration Guide. The selected POA can obtain information about all users in all post offices in your GroupWise system, if your GroupWise system has a GroupWise name server, as described in Simplifying Client/Server Access with a GroupWise Name Server in Post Office Agent in the GroupWise 8 Administration Guide. The Mobility Pack Installation program and the GroupWise Connector need the IP address or DNS hostname of the server where the POA is running. In addition, they need the POA SOAP port, which is 7191 by default. Typically, the same port number is used regardless of whether the POA is configured for a secure SSL SOAP connection. The Mobility Pack Installation program and the GroupWise Connector need to know whether or not the connection is secure, because they use one of the following URLs to communicate with the POA:

Under GroupWise Address Book User, specify a valid GroupWise user ID that the Mobility Connector can use to access the GroupWise Address Book to obtain contact information.
For more information about GroupWise Address Book visibility, see Controlling Object Visibility in System in the GroupWise 8 Administration Guide.
2.1.5 Gathering Mobile Device Information
The Mobility Connector needs certain configuration information about the mobile devices that it synchronizes GroupWise data with.
Mobile Device Port on page 25 Server Certificate on page 25 Incoming Devices on page 26
For device-specific instructions, see the Novell Data Synchronizer Mobility Connector Wiki (http:// wiki.novell.com/index.php/Data_Synchronizer_Mobility_Connector). Mobile Device Port By default, the Mobility Connector uses all available IP addresses on the server where you install the Mobility Pack. You can bind the Mobility Connector to a specific IP address after installation, as described in Binding to a Specific IP Address in Mobility Connector Configuration in the Mobility Connector Installation and Configuration Guide. Typically, the Mobility Connector uses port 443 for secure SSL HTTP connections with mobile devices and port 80 for non-secure HTTP connections. If mobile devices connect directly to the Mobility Connector, a secure HTTP connection is strongly recommended. If mobile devices connect to the Mobility Connector through a security application such as Novell Access Manager, the Mobility Connector can appropriately be configured with a non-secure HTTP connection.
Under Mobile Device Port, mark whether you want to configure the Mobility Connector to use a secure or non-secure HTTP port to communicate with mobile devices. Specify the port number used by the mobile devices that your Synchronizer system supports.
IMPORTANT: If there is a firewall between the Synchronizer server and users mobile devices, be sure to configure the firewall to allow communication on the selected HTTP port. Server Certificate In order to use a secure SSL HTTP connection between the Mobility Connector and mobile devices, a server certificate is required. If you do not already have a certificate signed by a certificate authority (CA) for the Synchronizer server, the Mobility Pack Installation program can create one for you. However, you should obtain a valid signed certificate as soon after installation as possible.

2.1.6 Planning the Data Synchronizer Database
When you run the Mobility Pack Installation program, it creates a PostgreSQL database that is used to store Synchronizer system configuration information that you see in Synchronizer Web Admin. It also stores pending events when synchronization between the Sync Engine and connectors is interrupted. The Synchronizer database is named datasync, and the user that has access is named datasync_user. You must supply the password for the Synchronizer database user.
Under Synchronizer Database, specify the password that you want to use for the Synchronizer database.
The Mobility Connector uses a secondary database named mobility to store events when synchronization between the Mobility Connector and mobile devices is interrupted. This includes the e-mail, contacts, appointments, calendars, and attachments that are synchronizing to and from mobile devices. The mobility database initially uses the same username and password as the datasync database.
If you need to change the password on either of these databases after you have installed the Mobility Pack, see:
Changing the Synchronizer Database Password in Managing a Synchronizer System in the
Novell Data Synchronizer System Administration Guide
Changing the Mobility Connector Database Password in Mobility Connector
Configuration in the Mobility Connector Installation and Configuration Guide
2.1.7 Establishing Data Synchronizer System Security
Configuration and administration of your Synchronizer system is performed through Synchronizer Web Admin. From Synchronizer Web Admin, you can:
Add connectors to your Synchronizer system Add users to connectors Start, stop, and configure connectors Reconfigure the connection to your LDAP server Reconfigure the Sync Engine
To protect your Synchronizer system operation and configuration, you must choose one LDAP administrator user to access Synchronizer Web Admin. This LDAP user becomes the initial Synchronizer administrator. For simplest administration, use the LDAP Admin user or an adminequivalent user. If you prefer to establish a Synchronizer administrator user with fewer rights than the LDAP Admin user, make sure the user has sufficient rights to read the User and Group objects that you need to access as you add users to connectors in Synchronizer Web Admin. Make sure that you know this administrator users password.

2.2.2 Preparing the Network
1 Make sure that any firewalls between the Synchronizer server and other applications have been configured to allow communication on the following ports:

Port Number

On Server

Description

636/4500 443/80 8120
LDAP POA Synchronizer Synchronizer Synchronizer
LDAP server secure or non-secure port GroupWise Post Office Agent (POA) SOAP port GroupWise Connector listening port for event notifications Mobile device secure or non-secure port Synchronizer Web Admin port
GroupWise Post Office Agent

port 636/389

port 7191

port 4500

port 8120

port 443/80

The GroupWise Connector initially communicates with the POA that you specify during Mobility Pack installation on the SOAP port that you specify. As users connect their mobile devices, the GroupWise Connector determines from the initial POA the IP addresses and port numbers of all POAs where mobile device users have their mailboxes. Therefore, the GroupWise Connector can communicate with multiple POAs throughout your GroupWise system.
2.2.3 Disabling an Existing Web Server
If necessary, stop and disable any existing Web server that is currently running on the Synchronizer server. For example, to stop the Apache Web server and its associated instance of Tomcat: 1 In a terminal window, become root by entering su - and the root password. 2 Enter the following commands to stop Apache and Tomcat:
/etc/init.d/tomcat5 stop /etc/init.d/apache2 stop
3 Enter the following commands to make sure that Apache and Tomcat do not start again when you reboot the Synchronizer server:
chkconfig --del apache2 chkconfig --del tomcat5
2.2.4 Verifying GroupWise System Availability
1 Make sure that the GroupWise trusted application key for the GroupWise Connector is accessible to the Mobility Pack Installation program on the Synchronizer server. For more information, see GroupWise Trusted Application on page 22. 2 Make sure that the GroupWise POA that the GroupWise Connector will communicate with is currently running.
2.2.5 Verifying Certificate Availability
1 (Conditional) If you have a signed certificate from a certificate authority (CA) as required for configuring secure HTTP connections with mobile devices: 1a Make sure that the certificate file is accessible to the Mobility Pack Installation program on the Synchronizer server. 1b (Conditional) If the key file that you received with the certificate included a password, make sure that the password has been removed. 1c (Conditional) If you received the certificate as multiple files, make sure that you have combined the files into one certificate file. 2 (Conditional) If you chose to use YaST to generate a self-signed certificate, make sure that it was created to include the specific DNS hostname of the Synchronizer server. 3 If possible, do not use a wildcard certificate. For best results, use a certificate that is created specifically for the Synchronizer server. For more information, see Securing Communication between the Mobility Connector and Mobile Devices (Mobility Pack Only) in Securing a Synchronizer System in the Novell Data Synchronizer System Administration Guide. For device-specific certificate issues, see Data Synchronizer Mobility Connector SSL Issues (http:// wiki.novell.com/index.php/Data_Synchronizer_Mobility_Connector_SSL_Issues).

2.3 Installing and Setting Up a Data Synchronizer System
You should already have reviewed Chapter 2.1, Planning a Data Synchronizer System, on page 17 and filled out the Mobility Pack Installation Summary Sheet. NOTE: If you are setting up a multi-server Synchronizer system, you should have a Summary Sheet for each Synchronizer server. Each Synchronizer server is independent of other Synchronizer servers, so you can set them up in whatever order is convenient given the overall configuration of your Synchronizer system.
The following sections step you through the process of installing the Mobility Pack and configuring a Synchronizer server.
Section 2.3.1, Running the Mobility Pack Installation Program, on page 31 Section 2.3.2, Checking the Status of the Data Synchronizer Services, on page 33 Section 2.3.3, Checking the Status of the Connectors, on page 34 Section 2.3.4, Managing Initial Device Synchronization, on page 35 Section 2.3.5, Testing Your Data Synchronizer System, on page 36 Section 2.3.6, Uninstalling the Mobility Pack, on page 37
2.3.1 Running the Mobility Pack Installation Program
1 Download the Novell Data Synchronizer Mobility Pack ISO file from Novell Downloads (http://download.novell.com) to a convenient temporary directory:
novell-datasynchronizer-mobility-pack-version.iso
2 On your Linux desktop, click Computer > YaST, then enter the root password. 3 Under Groups, click Software, then click Add-On Products. 4 On the Installed Add-On Products page, click Add, select Local ISO Image, then click Next.
5 In the Repository Name field, specify a name for the repository that will hold the Mobility Pack software, such as Mobility Pack. 6 In the Path to ISO Image field, browse to and select the ISO file that you downloaded in Step 1, then click Next. 7 Accept the License Agreement, then click Next. 8 In the Filter field, ensure that Patterns is selected. 9 Under Primary Functions, select Novell Data Synchronizer Mobility Pack.
10 Click Accept to start the installation. 11 Click Continue to acknowledge the automatic changes to other aspects of your system that will be made as the Mobility Pack software is installed
IMPORTANT: Do not click Next at this point. 12 After the software has been installed, click Change > Mobility Pack Configuration to configure your Synchronizer system. 13 Use the information that you have gathered on the Mobility Pack Installation Summary Sheet to provide the information that the Mobility Pack Installation program prompts you for, clicking Next to move from page to page. LDAP Server Settings: LDAP Server IP Address or Hostname LDAP Port Secure LDAP Admin DN LDAP Admin Password Data Synchronizer Settings: LDAP User Container LDAP Group Container Data Synchronizer Admin DN Data Synchronizer Database Password GroupWise Connector Settings: Trusted Application Name Trusted Application Key File GroupWise Post Office Agent IP Address or Hostname SOAP Port Secure Mobility Connector Settings: Device Port

4b Verify that all users have been successfully added. 4c Click Home to return to the main Synchronizer Web Admin page. 5 Verify that the users and groups that you selected during installation have been added to the Mobility Connector: 5a Click the Mobility Connector, then click Users.
5b Verify that all users have been successfully added. 5c Click Home to return to the main Synchronizer Web Admin page. 6 (Conditional) If any users were not successfully added during installation, you can add them manually afterwards and then verify that they have been added. See Appendix A, Mobility Pack Installation Troubleshooting, on page 49 for instructions
2.3.4 Managing Initial Device Synchronization
IMPORTANT: If users LDAP usernames are not the same as their GroupWise user IDs, you must update their application names in Synchronizer Web Admin before initial device synchronization can succeed. For instructions, see Changing a Users Application Name (Mobility Pack Only) in Managing Connectors and Users in the Novell Data Synchronizer System Administration Guide. Initial device synchronization provides the following synchronization of GroupWise items:
Contacts from all personal address books, excluding the Frequent Contacts address book
You can change this personal address book selection setting for users after installation in Synchronizer Web Admin, as described in Customizing a Users Synchronization Settings in Managing Connectors and Users in the Novell Data Synchronizer System Administration Guide. Users can also change their own synchronization settings on the User Options page in Synchronizer Web Admin. The GroupWise Address Book cannot be synchronized to mobile devices. However, users can still access individual contacts in the GroupWise Address Book, if their mobile devices can do a Global Address List (GAL) lookup. As an alternative, users can create a personal address book that is a subset of the GroupWise Address Book to synchronize to their mobile devices.
Calendar items (appointments and reminder notes) from the last two weeks and all future items
If shared calendars are important to users, shared calendar owners can post them to the Internet using the GroupWise Calendar Publishing Host, as described in Publishing Personal Calendars on the Internet in Calendar in the GroupWise 8 Windows Client User Guide. After the owner publishes the calendar, other users can view the calendar URL in the Web browser on their mobile devices. For Calendar Publishing Host setup instructions, see Installing the GroupWise Calendar Publishing Host in the GroupWise 8 Installation Guide.

E-mail messages in the Mailbox folder for the last three days
If users want to receive more existing e-mail messages on their devices, they can their mobile devices to request additional existing e-mail messages.
Folders in the Cabinet (but not items in folders until users request them by opening folders on
their mobile devices) In Synchronizer Web Admin, you can monitor the progress of data synchronization from GroupWise to the Mobility Connector, as described in Monitoring Mobility Connector Synchronization Status in Synchronization Monitoring and Management in the Mobility Connector Installation and Configuration Guide. IMPORTANT: If you selected Block Incoming Devices during Mobility Pack installation, you must unblock incoming devices in Synchronizer Web Admin after all GroupWise data has synchronized to the Mobility Connector. Follow the instructions in Blocking/Unblocking Incoming Devices before Initial Synchronization in Mobility Connector Configuration in the Mobility Connector Installation and Configuration Guide. Users must configure their mobile devices to connect to your Synchronizer system, as described in the Novell Data Synchronizer Connector for Mobility Quick Start (http://www.novell.com/ documentation/datasync_connectors1/mobilityconnect11_qs/data/mobilityconnect11_qs.html). For information about general device configuration, initial device synchronization, and ongoing synchronization, see the Mobility Connector Quick Start on the Novell Data Synchronizer Documentation Web site (http://www.novell.com/documentation/datasync_connectors1). For device-specific information, see the Novell Data Synchronizer Mobility Connector Wiki (http:// wiki.novell.com/index.php/Data_Synchronizer_Mobility_Connector).
2.3.5 Testing Your Data Synchronizer System
1 Test your Synchronizer system by logging into the GroupWise client and sending yourself an email message 2 Reply to the message from your mobile device. If the message synchronizes to your mobile device and the reply on your mobile device synchronizes back to GroupWise, your basic Synchronizer system is up and running. 3 To customize and expand your Synchronizer system, see Chapter 2.4, Whats Next, on page 37.
2.3.6 Uninstalling the Mobility Pack
IMPORTANT: When you uninstall the Mobility Pack software, certificate files are also deleted. If you have obtained commercially signed certificates for use in your Synchronizer system, back them up before uninstall the Mobility Pack software. 1 In a terminal window on the Synchronizer server, become root by entering su - and the root password. 2 Change to the following directory:

LDAP (network) passwords GroupWise (mailbox)
passwords Enable GroupWise Authentication?
See LDAP Passwords vs. GroupWise Passwords on page 19.

Mobility Pack Update

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.
Section 3.1, Updating to the Next Major Version (Mobility Pack 1 to Mobility Pack 1.1), on

page 43

Section 3.2, Updating to the Next Minor Version (Mobility Pack 1.1.x), on page 45
3.1 Updating to the Next Major Version (Mobility Pack 1 to Mobility Pack 1.1)
When you update from Mobility Pack 1 to Mobility Pack 1.1, you obtain the Mobility Pack 1.1 ISO from the Novell Customer Center or from the Novell Download Web site. Then you use YaST to update your Synchronizer system to Mobility Pack 1.1.
Section 3.1.1, Obtaining the Mobility Pack 1.1 ISO from the Novell Customer Center, on
Section 3.1.2, Obtaining the Mobility Pack 1.1 ISO from the Novell Downloads Web Site, on
Section 3.1.3, Installing the Next Version, on page 44
3.1.1 Obtaining the Mobility Pack 1.1 ISO from the Novell Customer Center
1 Log in to the Novell Customer Center (http://www.novell.com/customercenter). 2 In the Select an Organization to Manage drop-down list, select your organization that is entitled to the Mobility Pack. 3 Click My Products, then click Novell GroupWise. 4 Under Novell GroupWise 8, locate Novell Data Synchronizer Mobility Pack 1.1, then click Media. 5 Click Proceed to Download, then follow the online instructions to download the Mobility Pack 1.1 ISO to a convenient temporary directory on the Synchronizer server. 6 Skip to Installing the Next Version on page 44.
3.1.2 Obtaining the Mobility Pack 1.1 ISO from the Novell Downloads Web Site
NOTE: This procedure can also be used to install minor versions if you prefer not to receive updates automatically through the Novell Update channel of the Novell Customer Center. 1 On Novell Downloads (http://download.novell.com), click Search Patches.
IMPORTANT: The Mobility Pack 1.1 software is located in the Patches list, not the Products list. 2 Select Data Synchronizer, then click Search. 3 Under Data Synchronizer Mobility Pack 1.1, click Novell Data Synchronizer Mobility Pack 1.1 x86-64. 4 Click Proceed to Download, then follow the online instructions to download the Mobility Pack 1.1 ISO to a convenient temporary directory on the Synchronizer server. 5 Continue with Installing the Next Version
3.1.3 Installing the Next Version
Using Patch CD Update in YaST on page 44 Running the Mobility Pack Update Script on page 44 Restarting the Synchronizer Services on page 45

Using Patch CD Update in YaST 1 Under Groups, click Software, then click Patch CD Update. 2 Click Next to start the update. 3 Select Local ISO Image, then click Next. 4 In the Repository Name field, specify a name for the repository for the Mobility Pack update software. 5 In the Path to ISO Image field, specify the full pathname to the Mobility Pack update ISO file, then click Next. 6 Click Yes to accept the License Agreement, then click Next. 7 On the Distribution Upgrade Settings page, click Next. 8 In the Confirm Update dialog box, click Start Update. 9 On the Novell Customer Center Configuration page, select Configure Later, then click Next. You can register to receive updates through the Novell Update channel of the Novell Customer Center when you update to Mobility Pack 1.1.x. 10 (Conditional) If you receive a message that no changes were made to the list of registered repositories and offering to let you rerun the registration, click No, Skip It. 11 On the Installation Completed page, click Finish. 12 Continue with Running the Mobility Pack Update Script. Running the Mobility Pack Update Script Running the Update script updates the Synchronizer database (datasync) and the Mobility database (mobility) for use with the updated software. 1 Change to the following directory:
2 Execute the Update script:

./update.sh

3 Continue with Restarting the Synchronizer Services. Restarting the Synchronizer Services 1 Stop the Synchronizer services:

rcdatasync stop

2 Verify that all Synchronizer services have stopped:

ps -eaf | grep datasync

3 Start the Synchronizer services:

rcdatasync start

4 Verify that major update has been installed: The version number is displayed at the bottom of the main Synchronizer Web Admin page.
3.2 Updating to the Next Minor Version (Mobility Pack 1.1.x)
Whether you are updating from a major release such as Mobility Pack 1.1 or a minor release such as Mobility Pack 1.0.x, the procedure is the same.
Section 3.2.1, Obtaining the Mobility Pack Activation Code from the Novell Customer

Center, on page 45

Section 3.2.2, Registering to Receive Mobility Pack Updates through the Novell Update

Channel, on page 46

Section 3.2.3, Applying a Minor Update to the Synchronizer Server, on page 46 Section 3.2.4, Running the Mobility Pack Update Script, on page 46 Section 3.2.5, Restarting the Synchronizer Services, on page 46
NOTE: If you prefer not to receive minor updates through the Novell Update channel of the Novell Customer Center, you can use the same procedure to install the minor update that you used to install the last major update.
3.2.1 Obtaining the Mobility Pack Activation Code from the Novell Customer Center

1 Log in to the Novell Customer Center (http://www.novell.com/customercenter). 2 In the Select an Organization to Manage drop-down list, select your organization that is entitled to the Mobility Pack. 3 Click My Products, then click Novell GroupWise. 4 Under Novell GroupWise 8, locate Novell Data Synchronizer Mobility Pack 1.1, then make a note of the activation code in the Code field. 5 Continue with Registering to Receive Mobility Pack Updates through the Novell Update Channel.
3.2.2 Registering to Receive Mobility Pack Updates through the Novell Update Channel
1 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 activation code that you obtained from the Novell Customer Center in Obtaining the Mobility Pack Activation Code from the Novell Customer Center on page 45. 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. You can then choose when to install each minor update. 2 Enter the following command to verify that the Novell Update channel for the Mobility Pack has been added on your Synchronizer server:

zypper ca

This command lists all product-specific channels where you are registered to receive updates. The following Mobility Pack update channel should be listed:

Alias Name

nu_novell_com:Mobility-1.1-Updates

Mobility-1.1-Updates

3 Continue with Applying a Minor Update to the Synchronizer Server.
3.2.3 Applying a Minor Update to the Synchronizer Server
1 Enter the following command:
zypper up -r nu_novell_com:Mobility-1.1-Updates
Several Mobility Pack packages are listed for update through the channel. 2 Enter YES to start the update process. 3 Continue with Running the Mobility Pack Update Script
3.2.4 Running the Mobility Pack Update Script
Running the Update script updates the Synchronizer database (datasync) and the Mobility database (mobility) for use with the updated software. 1 Change to the following directory:
3 Continue with Restarting the Synchronizer Services.
3.2.5 Restarting the Synchronizer Services
1 Stop the Synchronizer services:
Mobility Pack Installation Troubleshooting
The Mobility Pack Installation program does not behave as documented. on page 49 The Mobility Pack Installation program cannot communicate with the LDAP server on

page 49

You cannot add an LDAP group during Mobility Pack installation on page 50 The Mobility Pack Installation program cannot communicate with a needed application. on