2
GroupWise Mobility Service System
Requirements
Before you install the GroupWise Mobility Service, ensure that the Mobility server meets the following system requirements:
Section 2.1, “Mobility Server Requirements,” on page 11
Section 2.2, “Directory Requirements,” on page 12
Section 2.3, “Web Browser Requirements for the Mobility Admin Console,” on page 12
Section 2.4, “GroupWise Requirements,” on page 12
Section 2.5, “Mobile Device Requirements,” on page 13
Section 2.6, “Recommended Number of Devices,” on page 14
2.1 Mobility Server Requirements
This section lists the minimum requirements for GroupWise Mobility Service. To see the recommended requirements for one server supporting approximately 750 users and 1000 devices,
see Section 2.6, “Recommended Number of Devices,” on page 14
.
Hardware requirements for the Mobility server:
x86-64 processor
2.2 GHz processor; multi-processor system recommended
Static IP address
Adequate server memory depending on the number of devices supported by the Mobility server
4 GB RAM to support approximately 300 devices
8 GB RAM to support up to the maximum of 750 users with up to 1000 devices
45 MB of disk space for the Mobility Service 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
Mobility Service log files, and other variables specific to your Mobility system implementation.
The largest consumers of disk space are the Mobility database (/var/lib/pgsql) and
Mobility Service log files (/var/log/datasync). You might want to configure the Mobility 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 Mobility server with a heavy load supporting approximately 750 users with up to 1000 devices. A Mobility server supporting substantially fewer devices requires substantially less disk space.
GroupWise Mobility Service System Requirements 11
SUSE Linux Enterprise Server (SLES) 11 (64-bit), plus Service Pack 3 or Service Pack 4
PostgreSQL
If PostgreSQL is not already installed on the Mobility server, the Mobility Service Installation program installs it for you.
Time synchronization
For the most reliable synchronization of time-sensitive items, such as appointments, the Mobility server and GroupWise servers should have their time synchronized as closely as possible. This is especially important on virtual machines.
In order for you to log in to the Mobility Admin console, your workstation and the Mobility server should have their time synchronized.
2.2 Directory Requirements
The GroupWise Mobility Service obtains users and groups from an LDAP directory or a GroupWise system.
Lightweight Directory Access Protocol (LDAP) v3
Any shipping version of NetIQ eDirectory fills this requirement. The GroupWise 2014 R2 LDAP server also fills this requirement.
or
GroupWise 2014 R2
See Section 2.4, “GroupWise Requirements,” on page 12
for complete details.
2.3 Web Browser Requirements for the Mobility
Admin Console
Any of the following web browsers:
Mozilla Firefox 20 or later
Microsoft Internet Explorer 10 or later
Safari 6 or later
Google Chrome 35 or later
2.4 GroupWise Requirements
In order for Mobility to interact successfully with a GroupWise POA, your GroupWise system must meet the following requirements:
GroupWise 2014 or later for post offices that have Mobility users.
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. For more information, see GroupWise System Creation in the GroupWise 2014 R2
Installation Guide .
12 GroupWise Mobility Service 2014 R2 Installation Guide
The GroupWise Post Office Agent (POA) that the GroupWise Sync Agent communicates with must have SOAP enabled.
The POA must also be configured with an HTTP user name and password on the Agent Settings property page of the POA object in the GroupWise Admin console (or in ConsoleOne in older
GroupWise systems). This enables you to monitor SOAP threads in the POA web console.
The initial POA uses the native GroupWise redirection process to inform the GroupWise Sync
Agent how to communicate with the additional POAs throughout your GroupWise system.
Thereafter, the GroupWise Sync Agent communicates directly with each POA where mobile device users’ mailboxes are located.
IMPORTANT: All POAs must have the same SSL setting--ether all enabled for SSL or all disabled for SSL. A tool has been created to help you test these settings. For information on this tool, see GMSsslCheck in the GroupWise Mobility Service 2014 R2 Security Enhancements
Quick Start .
A GroupWise trusted application key is required so that the GroupWise Sync Agent canauthenticate to GroupWise mailboxes without needing GroupWise users’ mailbox passwords. For more information, see Creating a Trusted Application and Key in the GroupWise
2014 R2 Administration Guide .
A Mobility server can be configured to communicate with one GroupWise system. If you have multiple GroupWise systems, you must set up a Mobility server for each GroupWise system.
2.5 Mobile Device Requirements
The Device Sync Agent communicates with mobile devices by using the Microsoft ActiveSync protocol version 14.x.
If a mobile device uses an earlier version of ActiveSync, the device can still successfully communicate with the Device Sync Agent, but functionality specific to 14.x is not available. If a mobile device uses a later version of ActiveSync, the device can still successfully communicate with the
Device Sync Agent, because later versions of ActiveSync are backward compatible with version 14.x.
Supported mobile device operating systems include:
Android 3.x, 4.x, and 5.x
Apple iOS 5.x, 6.x, 7.x, 8.x, and 9.x
Windows Phone 7
Windows 8 (Phone, Tablet, and Desktop)
BlackBerry 10.x
A user can synchronize data to multiple mobile devices as needed.
For the latest information about supported mobile devices, see the GroupWise Mobility Service
Devices Wiki (http://wiki.novell.com/index.php/GroupWise_Mobility_Devices) .
Mobile devices communicate directly with the Device Sync Agent 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. Your mobile device carrier is not involved in the synchronization process.
NOTE: The Device Sync Agent does not work with POP, IMAP, SMTP, or other message transfer protocols.
GroupWise Mobility Service System Requirements 13
2.6 Recommended Number of Devices
The following are the recommended requirements for a single Mobility server. For the minimum requirements, see
Section 2.1, “Mobility Server Requirements,” on page 11 .
A single Mobility server can comfortably support approximately 750 users with up to 1000 devices.
The following variables were taken into consideration for this configuration:
Server configuration
System configuration
Level of user activity, both in GroupWise and on their mobile devices
Server Configuration
Virtual machine
2.8 GHz processor
4 CPUs
8 GB RAM
Mobility System Configuration
750 users
1000 devices
User/Device Traffic
Average of 181 GroupWise events per minute
Email send / read / move to folder / delete
Appointment send / accept / decline / delete
Folder create
Average of 474 events per user in a 24-hour period
Average of 165 device requests per minute
Email send / read
Average of 427 emails from devices in a 24-hour period
Average of 2479 KB per minute of attachment data transfer
97% under 1 MB
2% between 1 MB and 2 MB
1% above 2 MB
NOTE: You can observe some of these statistics for your own Mobility system using the Dashboard in the Mobility Admin console. For more information, see “ Using the Mobility Dashboard ” in the
GroupWise Mobility Service 2014 R2 Administration Guide .
Device Profile
60% Apple devices
14 GroupWise Mobility Service 2014 R2 Installation Guide
37% Android devices
10% Windows Mobile devices
3% Other
Hardware Performance for Four Days
24% average CPU usage
17% average disk busy usage
26% average memory usage, with 32% maximum and 24% minimum
GroupWise Mobility Service System Requirements 15
16 GroupWise Mobility Service 2014 R2 Installation Guide
