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.
Hardware requirements for the Mobility server:
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.
SUSE Linux Enterprise Server (SLES) 11 (64-bit), plus Service Pack 3
If PostgreSQL is not already installed on the Mobility server, the Mobility Service Installation program installs it for you.
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.