2.8 GHz multi-processor system with a 4-Core CPU recommended
Static IP address
Adequate server memory depending on the number of devices supported by the Mobility server
8 GB RAM to support approximately 300 devices
12 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/mobility/attachments directory.
Mobility is supported on SLES 15 SP2. Make sure your server meets the base server requirements and the requirements for the version of SLES you are using.
NOTE:Mobility is not supported on OES.
Install on a Dedicated Server: You should install GroupWise Mobility on its own server (virtual or physical) separate from other applications, including GroupWise.
Specify only EXT4 as the GMS server’s File System: SLES 15 SP2 defaults to BTRFS and you must manually change this to EXT4.
Do not use a Proxy Server with GMS: Using a proxy server causes problems with the Mobility connection to the GroupWise server.
Registration Is Required to Receive Updates: Your SLES server must be registered to receive the packages necessary to install Mobility.
DNS Is Required: Your Mobility server must be DNS resolvable.
Time Synchronization Is Required: 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.
SLES 15 SP2 requires the following SLES modules/extension before you can install Mobility:
Basesystem Module 15 (included with registration)
Server Applications Module (included with registration)
Desktop Applications Module (provides GNOME desktop)
SUSE Package Hub
The easiest way to add modules and extensions is during the SLES 15 SP2 install. For more information on modules and extensions, see the SLES 15 Modules & Extensions Quick Start.