Novell DATA SYNCHRONIZER - 07-2010 User manual

Novell®
www.novell.com
novdocx (en) 16 April 2010
AUTHORIZED DOCUMENTATION
Novell Data Synchronizer Mobility Pack Installation Guide
Data Synchronizer Mobility Pack
Public Beta
July 14, 2010
Installation Guide

novdocx (en) 16 April 2010
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. See
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.
Novell, Inc.
404 Wyman Street, Suite 500
Waltham, MA 02451
U.S.A.
www.novell.com
Online Documentation: To access the online documentation for this and other Novell products, and to get updates,
see the Novell Documentation Web site (http://www.novell.com/documentation).

novdocx (en) 16 April 2010
Novell Trademarks
For Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/
trademarks/tmlist.html).
Third-Party Materials
All third-party trademarks are the property of their respective owners.

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

Contents 5
Contents
novdocx (en) 16 April 2010
About This Guide 7
1 Product Overview 9
1.1 What Is Data Synchronizer? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.1.1 Data Synchronizer Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.1.2 Data Synchronizer Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.1.3 Data Synchronizer Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.2 Data Synchronizer System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.2.1 Data Synchronizer Server Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.2.2 Directory Service Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.2.3 Web Browser Requirements for Synchronizer Web Admin . . . . . . . . . . . . . . . . . . . . 13
1.2.4 Connector Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2 Mobility Pack Installation 15
2.1 Planning a Data Synchronizer System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.1.1 Planning Your Data Synchronizer System Configuration . . . . . . . . . . . . . . . . . . . . . 15
2.1.2 Gathering LDAP Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.1.3 Planning How to Add Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.1.4 Gathering GroupWise System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.1.5 Gathering Mobile Device Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.1.6 Planning the Data Synchronizer Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.1.7 Establishing Data Synchronizer System Security . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.2 Setting Up Your Data Synchronizer System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.2.1 Performing Pre-Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.2.2 Running the Data Synchronizer Mobility Pack Installation Program . . . . . . . . . . . . . 25
2.2.3 Checking the Status of the Data Synchronizer Services . . . . . . . . . . . . . . . . . . . . . . 27
2.2.4 Checking the Status of the Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.2.5 Managing Initial Device Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.2.6 Testing Your Data Synchronizer System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.2.7 Uninstalling the Mobility Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3 What’s Next 31
3.1 Managing Your Data Synchronizer System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.2 Managing the GroupWise Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.3 Managing the Mobility Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.4 Installing Additional Connectors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4 Mobility Pack Installation Summary Sheet 33
A Mobility Pack Troubleshooting 35

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

About This Guide 7
novdocx (en) 16 April 2010
About This Guide
The Novell Data Synchronizer Mobility Pack Installation Guide helps you to understand and set up
a Data Synchronizer system by installing the Data Synchronizer Mobility Pack, which consists of
Data Synchronizer, the GroupWise Connector, and the Mobility Connector. The guide is divided
into these sections:
Chapter 1, “Product Overview,” on page 9
Chapter 2, “Mobility Pack Installation,” on page 15
Chapter 3, “What’s Next,” on page 31
Chapter 4, “Mobility Pack Installation Summary Sheet,” on page 33
Appendix A, “Mobility Pack Troubleshooting,” on page 35
Audience
This guide is intended for network administrators who install and administer Data Synchronizer to
provide data synchronization between GroupWise and mobile devices.
Feedback
We want to hear your comments and suggestions about this manual and the other documentation
included with this product. Please use the User Comment feature at the bottom of each page of the
online documentation, or go to Novell Documentation Feedback (http://www.novell.com/
documentation/feedback.html) and enter your comments there.
Additional Documentation
For additional Data Synchronizer documentation, see the following documentation provided 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
For additional Data Synchronizer connector documentation, see the following documentation
provided at the Novell Data Synchronizer Connectors Documentation Web site (http://
www.novell.com/documentation/datasync_connectors1).
Connector Readmes
Connector Quick Starts
Connector installation and configuration guides
For device-specific setup instructions, see the Novell Data Synchronizer Mobility Connector Wiki
(http://wiki.novell.com/index.php/Data_Synchronizer_Mobility_Connector).

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

Product Overview
1
9
novdocx (en) 16 April 2010
1
Product Overview
Section 1.1, “What Is Data Synchronizer?,” on page 9
Section 1.2, “Data Synchronizer System Requirements,” on page 12
1.1 What Is Data Synchronizer?
Novell Data Synchronizer allows personal information management (PIM) data such as e-mail,
appointments, tasks, and contacts to synchronize between enterprise e-mail and collaboration
applications such as Novell GroupWise, other collaboration applications, and mobile devices. It is a
bi-directional and many-to-many synchronization solution that can connect multiple collaboration
applications and mobile devices, providing real-time, event-driven synchronization.
Section 1.1.1, “Data Synchronizer Capabilities,” on page 9
Section 1.1.2, “Data Synchronizer Components,” on page 9
Section 1.1.3, “Data Synchronizer Configurations,” on page 12
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 device operating systems are supported, including Android, Apple,
Maemo, Palm, Symbian, and Windows Mobile.
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 10.
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.
“Sync Engine” on page 9
“Web Administration Service” on page 10
“Configuration Engine” on page 10
“Connector Manager” on page 10
“Connectors” on page 10
Sync 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 other applications through their
connectors.

10 Novell Data Synchronizer Mobility Pack Installation Guide
novdocx (en) 16 April 2010
Figure 1-1 Sync Engine with Multiple Connectors
For example, when you install the Mobility Pack, you can synchronize data between GroupWise and
mobile devices. Then, if you also want to synchronize data between GroupWise and SugarCRM,
you add the SugarCRM Connector to your Synchronizer system. All connectors communicate with
each other through the Sync Engine.
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 Configuration 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
example, when you install the Mobility Pack, which includes the GroupWise Connector and the
Mobility Connector, GroupWise content can be synchronized to any mobile device that uses
Microsoft ActiveSync. Or, if you install add the SugarCRM connector to your Synchronizer system,
your GroupWise contact information can be synchronized with the contact information in
SugarCRM.

Product Overview 11
novdocx (en) 16 April 2010
Supported Applications
Data Synchronizer currently provides connectors for the following applications:
Novell GroupWise
Mobile devices that use the ActiveSync protocol
Salesforce.com
SharePoint
SugarCRM
Application Items
Each application has its own types of data (often called “items”) that would be useful to synchronize
with other applications. Some common types of items that can be synchronized between
applications include:
E-mail messages
Appointments
Tasks
Notes
Address books
Contacts
Folders
Not all connectors support all of the same types of items.
Synchronization Events
Initially, existing items are synchronized between applications. Which items are initially
synchronized varies from connector to connector.
As time passes, the following events can affect existing items, and the resulting changes in the items
are also synchronized:
Add
Modify
Move
Delete
Some connectors allow you to select which events you want to synchronize. With other connectors,
you cannot customize which events are synchronized.
Events and the item data associated with them flows through your Synchronizer system in the form
of XML files that are processed by the connectors and the Sync Engine in order to transfer data from
one application to another. You do not need this conceptual understanding of connector functionality
unless you need to troubleshoot a disruption to synchronization between two applications.

12 Novell Data Synchronizer Mobility Pack Installation Guide
novdocx (en) 16 April 2010
1.1.3 Data Synchronizer Configurations
When you install the Data Synchronizer Mobility Pack, the Synchronizer services, the GroupWise
Connector, and the Mobility Connector are all installed on the same server. The Synchronizer server
can have one instance of each connector. Multiple instances of the same connector cannot be created
on a single Synchronizer server.
A single-server Synchronizer system can meet the synchronization needs of approximately 200 to
300 users, depending on the amount of synchronization traffic generated by those users. You might
need to set up a Synchronizer system that includes multiple Synchronizer servers for the following
reasons:
Number of Users: You need to support synchronization for more than 200 to 300 users.
Location of Users: You need to support users that are located in distant geographical locations
where synchronization performance could be adversely affected by the network connections
between users and the applications that they want to synchronize data with.
Location of Synchronized Applications: Applications for which data is being synchronized
have meaningful organizational segments (for example, GroupWise domains and post offices).
Having a Synchronizer server associated with each organizational segment would help balance
the synchronization load across all users of the application.
Quality of Service: Certain segments of your user population, such as executives of your
organization, might expect and require a higher level of synchronization performance than
typical users. This higher quality of service can be accomplished by setting up a small
Synchronizer system specifically for such high profile users.
Connector-specific considerations for implementing a multi-server Synchronizer system are covered
in each connector’s Installation and Configuration Guide (http://www.novell.com/documentation/
datasync_connectors1).
1.2 Data Synchronizer System Requirements
You, as a Synchronizer administrator, must ensure that the Synchronizer server meets Synchronizer
system requirements, so that your Synchronizer system can function successfully.
Section 1.2.1, “Data Synchronizer Server Requirements,” on page 12
Section 1.2.2, “Directory Service Requirement,” on page 13
Section 1.2.3, “Web Browser Requirements for Synchronizer Web Admin,” on page 13
Section 1.2.4, “Connector Requirements,” on page 13
1.2.1 Data Synchronizer Server Requirements
Hardware requirements for the Synchronizer server:
64-bit/x86 processor
2.2 GHz processor; multi-processor system recommended
4 GB RAM
45 MB of disk space for the Synchronizer software
200 GB of disk space recommended for data storage during system operation

Product Overview 13
novdocx (en) 16 April 2010
Data storage disk space varies widely depending on the amount of data being
synchronized, the number of users participating in synchronization, the logging level for
Synchronizer log files, and other variables specific to your Synchronizer system
implementation.
The largest consumers of disk space are the Synchronizer database (
/var/lib/pgsql )
and Synchronizer log files (
/var/log/datasync ). You might want to configure the
Synchronizer server so that
/var is a on separate partition to allow for convenient
expansion.
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.
1.2.2 Directory Service Requirement
Lightweight Directory Access Protocol (LDAP) v3
1.2.3 Web Browser Requirements for Synchronizer Web Admin
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 for each connector:
GroupWise system requirements for the GroupWise Connector
Mobile device requirements for the Mobility Connector
Salesforce.com system requirements for the Salesforce.com Connector
SharePoint system requirements for the SharePoint Connector
SugarCRM system requirements for the SugarCRM Connector

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

Mobility Pack Installation
2
15
novdocx (en) 16 April 2010
2
Mobility Pack Installation
The Novell Data Synchronizer Mobility Pack Installation program available in YaST helps you
install Data Synchronizer, the GroupWise Connector, and the Mobility Connector to set up your
initial Synchronizer system.
Section 2.1, “Planning a Data Synchronizer System,” on page 15
Section 2.2, “Setting Up Your Data Synchronizer System,” on page 23
2.1 Planning a Data Synchronizer System
You can use the “Mobility Pack Installation Summary Sheet” on page 33 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 15
Section 2.1.2, “Gathering LDAP Information,” on page 15
Section 2.1.3, “Planning How to Add Users,” on page 17
Section 2.1.4, “Gathering GroupWise System Information,” on page 19
Section 2.1.5, “Gathering Mobile Device Information,” on page 21
Section 2.1.6, “Planning the Data Synchronizer Database,” on page 23
Section 2.1.7, “Establishing Data Synchronizer System Security,” on page 23
2.1.1 Planning Your Data Synchronizer System Configuration
A Synchronizer system can consist of a single Synchronizer server or multiple Synchronizer servers.
A single Synchronizer server can handle approximately 200 to 300 users, depending on the amount
of synchronization traffic generated by those users. For planning guidelines, review Section 1.1.3,
“Data Synchronizer Configurations,” on page 12.
If you plan to install the Mobility Pack on multiple servers, you can proceed through the following
planning sections server by server, or you can apply each planning section to all planned servers,
then proceed to the next planning section.
2.1.2 Gathering LDAP Information
The Data Synchronizer Mobility Pack Installation program needs access to an LDAP directory in
order to add users and groups to your Synchronizer system.
“LDAP Server Network Information” on page 16
DATA SYNCHRONIZER MOBILITY PACK INSTALLATION SUMMARY SHEET
Print one or more copies of the Mobility Pack Installation Summary Sheet, one for each Synchronizer
server that you are planning for your Synchronizer system.

16 Novell Data Synchronizer Mobility Pack Installation Guide
novdocx (en) 16 April 2010
“LDAP Server Credentials” on page 16
“LDAP User and Group Containers” on page 16
“LDAP Passwords vs. GroupWise Passwords” on page 17
LDAP Server Network Information
In order to communicate with your LDAP directory, the Mobility Pack Installation program needs
the IP address or DNS hostname of your LDAP server. It also needs the port number that the LDAP
server listens on. The LDAP port number depends on whether the LDAP server requires a secure
SSL connection. The default secure port number is 636. The default non-secure LDAP port number
is 389.
If the LDAP server requires a secure connection, additional setup might be required. See “Securing
Communication with the LDAP Server” in “Securing Your Synchronizer System” in the Novell
Data Synchronizer Administration Guide.
IMPORTANT: If there is a firewall between the Synchronizer server and the LDAP server, be sure
to configure the firewall to allow communication on the selected LDAP port.
LDAP Server Credentials
In order to access the LDAP directory, the Mobility Pack Installation program needs the username
and password of an administrator user on the LDAP server who has sufficient rights to access the
user and group information stored there. At least Read rights are required. You can use the
admin
LDAP user or an admin-equivalent user. You need to provide the username, along with its context in
your LDAP directory tree, in the following format:
cn=username,ou=organizational_unit,o=organization
LDAP User and Group Containers
During installation, the Mobility Pack Installation program lets you add users and groups to your
Synchronizer system from any location in the LDAP directory where the LDAP administrator user
has rights to read the user and group information. However, after installation, you use Synchronizer
Web Admin to add users and groups to your Synchronizer system.
During installation, you must provide a user container and a group container from which
Synchronizer Web Admin lists users and groups that you can add to your Synchronizer system. The
Installation program lets you browse for the user and group containers. It then displays the
containers in the following LDAP format:
ou=container_name,ou=organizational_unit,o=organization
DATA SYNCHRONIZER MOBILITY PACK INSTALLATION SUMMARY SHEET
Under LDAP Server Information, specify the IP address or DNS hostname of your LDAP server, and
mark whether a secure SSL connection is required.
DATA SYNCHRONIZER MOBILITY PACK INSTALLATION SUMMARY SHEET
Under LDAP Server Credentials, specify a fully qualified username with sufficient rights to read the user
and group information in your LDAP directory, along with the password for that user.

Mobility Pack Installation 17
novdocx (en) 16 April 2010
When Synchronizer Web Admin generates lists of users and groups, it searches the containers you
specify, as well as subcontainers. If you want Synchronizer Web Admin to be able to search
multiple, organizationally separate containers for users and groups, you can configure this
functionality after you have installed the Mobility Pack, as described in “Searching Multiple LDAP
Contexts for Users and Groups” in “Managing Your Synchronizer System” in the Novell Data
Synchronizer Administration Guide.
LDAP Passwords vs. GroupWise Passwords
Users use their LDAP passwords to log in to the network. They might or might not use the same
password to log in to their GroupWise mailboxes. The Mobility Pack Installation program
configures your Synchronizer system to use LDAP (network) passwords. If users have different
passwords for their GroupWise mailboxes, they must configure their mobile devices with their
LDAP (network) passwords, rather than their GroupWise passwords, in order to synchronize data
with their GroupWise mailboxes.
2.1.3 Planning How to Add Users
A number of variables affect how you add users to your Synchronizer system:
DATA SYNCHRONIZER MOBILITY PACK INSTALLATION SUMMARY SHEET
Under LDAP Containers, specify a container object and its context in the LDAP directory tree where User
objects are located. If Group objects are located in a different container, list that container as well.
DATA SYNCHRONIZER MOBILITY PACK INSTALLATION SUMMARY SHEET
Under GroupWise Authentication, mark whether users use LDAP (network) passwords or GroupWise
password to access their GroupWise mailboxes.
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, including the Frequent Contacts address
book
Calendar items (appointments, tasks, notes) from the last two weeks and all future
items
E-mail messages received after initial synchronization of the mobile device
Folders in the Cabinet (but not items in folders until users request them by opening
folders)
Adding at least a couple of users for testing purposes during installation is recommended.

18 Novell Data Synchronizer Mobility Pack Installation Guide
novdocx (en) 16 April 2010
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” in the Novell Data Synchronizer 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.
Setting
application
names
If users’ LDAP usernames are not the same as their GroupWise user IDs, you must set
users’ application names in Synchronizer Web Admin to map from LDAP usernames to
GroupWise user IDs. This must be done regardless of whether you add the users during
installation or after installation, and it applies to users who are added by being members
of LDAP groups. To plan ahead for this process, review “Changing a User’s Application
Name” in “Managing Connectors” in the Novell Data Synchronizer Administration Guide.
Single-server
installation
If you are planning a single-server Synchronizer system, you might already have or want
to create LDAP groups based on departmental membership, organizational roles,
geographic locations, or even the need to participate in data synchronization. For
example, if only a few users have mobile devices and they are scattered throughout a
number of existing LDAP groups, you might create a new LDAP group named
MobileDeviceUsers so that you can easily add them as a group to your Synchronizer
system.
Multi-server
installation
If you are planning a multi-server Synchronizer system, you might already have or want
to create LDAP groups that would be set up on different Synchronizer servers. You might
be planning several Synchronizer servers based on geographic location, so having an
LDAP group of users for each geographic location would facilitate adding users to
connectors. If you want a separate Synchronizer server for executives, creating an LDAP
group of executives would allow you to add them as a group, rather than selecting each
executive individually. If you have a very large number of groups with no particular
distinguishing characteristics, you might want to create LDAP groups based on the first
letter of users’ last names or usernames (for example, A-I, J-R, and S-Z).

Mobility Pack Installation 19
novdocx (en) 16 April 2010
Regardless of the variables involved in adding users to your Synchronizer system, advanced
planning can make the process of adding users easier and faster.
IMPORTANT: Be sure to add yourself to the Synchronizer system for testing purposes.
2.1.4 Gathering GroupWise System Information
In order to configure the GroupWise Connector as you run the Mobility Pack Installation program,
you need to gather certain information about the GroupWise system where users want to
synchronize data.
“GroupWise Trusted Application” on page 19
“GroupWise Post Office Agent” on page 20
“GroupWise Address Book User” on page 21
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.
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. When
setting 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.
DATA SYNCHRONIZER MOBILITY PACK INSTALLATION SUMMARY SHEET
Under Add Groups, specify LDAP groups of users to add to your Synchronizer system. If the LDAP
groups do not already exist, create them in your LDAP directory before you run the Mobility Pack
Installation program.
Under Add Users, specify any individual users that are not part of LDAP groups that you want to add to
your Synchronizer system.

20 Novell Data Synchronizer Mobility Pack Installation Guide
novdocx (en) 16 April 2010
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.
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, provided 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:
IMPORTANT: By default, the GroupWise Connector communicates with the POA using port
4500. If there is a firewall between the Synchronizer server and the POA server, be sure to configure
the firewall to allow communication on port 4500. If necessary, you can configure the GroupWise
Connector to use a different port number after installation, as described in “Changing the
GroupWise Connector Listening Port” in “GroupWise Connector Configuration” in the Groupwise
Connector Installation and Configuration Guide.
DATA SYNCHRONIZER MOBILITY PACK INSTALLATION SUMMARY SHEET
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.
Non-Secure SOAP URL:
http://poa_server_address:soap_port/soap
Secure SOAP URL:
https://poa_server_address:soap_port/soap
DATA SYNCHRONIZER MOBILITY PACK INSTALLATION SUMMARY SHEET
Under GroupWise Post Office Agent, specify the IP address or DNS hostname of the server where a
POA configured for SOAP is running. Specify the SOAP port, and whether or not the POA requires a
secure SSL SOAP connection.