Before you install the Mobility Pack, ensure that the Synchronizer server meets Synchronizer system requirements, so that your Synchronizer system can function successfully.
Hardware requirements for the Synchronizer server:
2.2 GHz processor; multi-processor system recommended
Adequate server memory depending on the number of devices supported by the Synchronizer server
4 GB RAM to support approximately 300 devices
8 GB RAM to support up to the maximum recommended number of devices
45 MB of disk space for the Synchronizer software
200 GB of disk space recommended for data storage during system operation
Data storage disk space varies widely depending on the amount of data being synchronized, the number of devices 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 on a separate partition to allow for convenient expansion.
Another large consumer of disk space is attachment storage in the /var/lib/datasync/syncengine/attachments directory.
NOTE:The 200 GB recommendation is appropriate for a large Synchronizer system that has the maximum recommended number of devices. A Synchronizer system with substantially fewer devices requires substantially less disk space.
Static IP address
SUSE Linux Enterprise Server (SLES) 11 (64-bit), plus Service Pack 2
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.
Lightweight Directory Access Protocol (LDAP) v3
Any version of Novell eDirectory fills this requirement. Other LDAP directories are not currently supported.
Any of the following Web browsers:
Mozilla FireFox 3 or later
Microsoft Internet Explorer 7 or later
Safari 3 or later
In order for the GroupWise Connector to interact successfully with your GroupWise system, your GroupWise system must meet the following requirements:
In post offices that have mobile device users:
GroupWise 2012 or later
GroupWise 8 Support Pack 2 or later
For best synchronization performance, the latest version of GroupWise is strongly recommended.
You must have at least a basic GroupWise system (one domain and one post office) set up and running, as described in
Installing a Basic GroupWise System in the GroupWise 2012 Installation Guide.
The GroupWise Post Office Agent (POA) that the GroupWise Connector communicates with must have SOAP enabled, as described in
Supporting SOAP Clients in
Post Office Agent in the GroupWise 2012 Administration Guide. It must also be configured with an HTTP user name and password on the Agent Settings property page of the POA object in ConsoleOne.
A GroupWise trusted application key is required so that the GroupWise Connector can authenticate to GroupWise mailboxes without needing GroupWise users’ mailbox passwords, as described in
Creating a Trusted Application and Key in
System in the GroupWise 2012 Administration Guide.
The Mobility Connector communicates with mobile devices by using the Microsoft ActiveSync protocol version 2.5. If a mobile device uses a later version of ActiveSync, the device can still successfully communicate with the Mobility Connector because later versions of ActiveSync are backward compatible with version 2.5.
Supported mobile device operating systems include:
Android 2.x, 3.x, and 4.1.x
Apple iOS 4.x, 5.x, and 6.0
Windows Mobile 6.x
Windows Phone 7
Windows 8 (Phone, Tablet, and Desktop)
Your mobile device communicates directly with the Mobility Connector to synchronize data. Some mobile devices require a data plan to accomplish this. Others work successfully with a Wi-Fi connection. Some mobile devices can be configured to use either method to communicate with the Mobility Connector. Your mobile device carrier is not involved in the synchronization process.
NOTE:The Mobility Connector does not work with POP, IMAP, SMTP, or other message transfer protocols. The Mobility Connector does not support BlackBerry devices. Instead, you must use BlackBerry Enterprise Server for GroupWise, as described in
BlackBerry Enterprise Server in
Mobile Devices in the GroupWise 2012 Interoperability Guide.
A user can synchronize data to multiple mobile devices as needed and can use multiple synchronization solutions as needed. For example, the Mobility Connector and BlackBerry Enterprise Server can both synchronize data from the same GroupWise mailbox without conflict.
For the latest information about supported mobile devices, see the Data Synchronizer Mobility Connector Devices Wiki.
A single Synchronizer server can comfortably support approximately 750 devices.
The performance of your Synchronizer system depends on many variables including server configuration, system configuration, and the level of user activity, both in GroupWise and on their mobile devices. This statement of support is based on the following testing parameters:
2.8 GHz processor
8 GB RAM
Synchronizer System Configuration
Average of 181 GroupWise events/minute
Email send / read/ move to folder / delete
Appointment send / accept / decline / delete
Average of 474 events/user in a 24-hour period
Average of 165 device requests/minute
Email send / read
Average of 427 emails from devices in a 24-hour period
Average of 2479 KB/minute of attachment data transfer
97% under 1MB
2% between 1MB and 2 MB
1% above 2 MB
NOTE:You can observe some of these statistics for your own Synchronizer system using the Global Status Monitor, as described in
Monitoring Your Synchronizer System in
Synchronizer System Management in the Mobility Pack Administration Guide.
60% Apple devices
37% Android devices
10% Windows Mobile devices
Hardware Performance for Four Days:
24% average CPU usage
17% average disk busy usage
26% average memory usage, with 32% maximum and 24% minimum