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 and other collaboration applications. It is a bi-directional and many-to-many synchronization solution that can connect multiple collaboration applications, providing real-time, event-driven synchronization.

1.1.1 Data Synchronizer Capabilities

A core Data Synchronizer system consists of the Synchronizer services and the GroupWise Connector. After you have created your core Synchronizer system, you can add additional connectors to synchronize GroupWise data with other supported applications, as described in Connectors.

Data Synchronizer and bi-directional connectors

For information about other connectors, visit the Data Synchronizer Connector Marketplace.

1.1.2 Data Synchronizer Components

Data Synchronizer consists of several components that are installed together on one server.

Data Synchronizer components

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 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.


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 Vibe OnPrem Connector to your core Synchronizer system, your Vibe OnPrem calendar and task information can be synchronized to your GroupWise Calendar and Tasklist.

Supported Applications

To find out about supported applications, see:

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.

NOTE: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.

1.1.3 Data Synchronizer Configurations

The Synchronizer services and the GroupWise Connector are installed together on the same server. Any connectors that you add to your core Synchronizer system must be installed on the same server with the Synchronizer services and the GroupWise Connector

Synchronizer System Configuration

The Synchronizer server must be able to communicate with other servers on your network.

Synchronizer System Configuration

For information about other connectors, visit the Data Synchronizer Connector Marketplace.


Required Configuration


The Synchronizer server can have one instance of each connector. Multiple instances of the same connector cannot be created on a single Synchronizer server.

LDAP Server

The Synchronizer server must be able to communicate with an LDAP server on your network during installation. If you need the Synchronizer server to communicate with multiple LDAP servers, additional setup is required, as described in LDAP Proxy Server to Multiple Sources.


The Synchronizer server must be able to communicate with the server where the application to synchronize with is installed. For example, if you are installing the Vibe OnPrem Connector, the Synchronizer server must be able to communicate with the Vibe OnPrem server.

Single Synchronizer Server System

The number of users that can be efficiently serviced by a Synchronizer system with a single Synchronizer server varies depending on the specific connectors that are participating in the Synchronizer system. See the System Requirements section of each connector’s Installation and Configuration Guide for the recommended number of users for the connectors you are installing in your Synchronizer system.

Multiple Synchronizer Server System

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 the recommended number of users for one or more of the connectors that you are installing.

  • 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 helps 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.