3.3 Installing GroupWise Mobility Service

Before you run the Mobility Service Installation program, ensure that you have done the following:

Review Planning a Mobility System.
Fill out the GroupWise Mobility Service Installation Worksheet.

If you are setting up a multi-server Mobility system, ensure that you have an Installation Worksheet for each Mobility server. Each Mobility server is independent of other Mobility servers, so you can set them up in whatever order is convenient, based on the overall configuration of your Mobility system.
Complete the tasks in Preparing to Install the Mobility Service.

The following sections step you through the process of installing the Mobility Service and configuring a Mobility system.

3.3.1 Obtaining the GroupWise Mobility Service 24.2 ISO

To download the GroupWise Mobility Service installation package:

GroupWise Mobility Service software is available through the OpenText Customer Care Center.
Download the GroupWise Mobility Service ISO to a convenient temporary directory on the Mobility server.
```
groupwise-mobility-service-24.2-x86_64-build_number.iso
```
Continue with Running the Mobility Service Installation Program.

3.3.2 Running the Mobility Service Installation Program

Mobility is supported on SLES 15 SP4, which uses an ISO based install.

If you encounter any problems during the installation, check the Mobility Service Installation program log file for information about the problem:

/var/log/datasync/install.log

For additional assistance, see GroupWise Mobility Service Installation Troubleshooting.

Before running the installation program, make sure your SLES 15 SP4 server meets all the of GroupWise Mobility Service System Requirements.
Browse to the location where the Mobility Service ISO is located in a terminal and mount the ISO by running the following command:
```
mount groupwise-mobility-service-24.2-x86_64-build_number.iso /mnt
```
Browse to /mnt in the terminal and run the following command to run the install:
```
./install.sh
```
NOTE:When prompted about the air gap install, you should enter “no” unless you are using an air gap-type environment where your GMS server is connected to a SLES Repository Mirroring Tool (RMT) to get any required SUSE packages without connecting directly to SUSE.

The Mobility Service Installation program creates the following directories and files:
```
/opt/novell/datasync
/usr/sbin/gms (symbolic link)
/etc/datasync
/var/lib/datasync
/var/log/datasync
/var/run/datasync
/var/lib/pgsql
```
Once the files have installed, use the GroupWise Mobility Service Installation Worksheet to configure GroupWise Mobility Service.

3.3.3 Checking the Status of the Mobility Service

The Mobility Service Installation program starts the Mobility Service for you. If the installation proceeded normally, all components of the Mobility Service should be running.

In a terminal window on the Mobility server, become root by entering su - and the root password.
Use the following command to check the status of the Mobility Service:
```
gms status
```
Use the following commands to manually start and stop the Mobility Service:
```
gms start
gms restart
gms stop
```

3.3.4 Using the Mobility Admin Console

The Mobility Service Installation program starts the GroupWise Sync Agent and the Device Sync Agent for you. Use the Mobility Admin console to check sync agent status.

In your web browser, access the Mobility Admin console at the following URL:
```
https://mobility_server_address:8120
```
Replace mobility_server_address with the IP address or DNS hostname of the server where the Mobility Service is installed.
Log in as the Mobility administrator.

The sync agents should display a status of Running.
(Conditional) If you encounter problems starting the sync agents, see the following troubleshooting resources:
- GroupWise Mobility Service Installation Troubleshooting
- GroupWise Mobility System Troubleshooting in the GroupWise Mobility Service Administration Guide
- Working with Log Files in the GroupWise Mobility Service Administration Guide
Skip to Adding Users to Your Initial Mobility System.

3.3.5 Uninstalling the Mobility Service

IMPORTANT:When you uninstall the Mobility Service software, certificate files are also deleted. If you have obtained commercially signed certificates for use in your Mobility system, back them up before you uninstall the Mobility Service software.

In a terminal window on the Mobility server, become root by entering su - and the root password.
Change to the following directory:
```
/opt/novell/datasync
```
Run the Mobility Uninstallation script:
```
./uninstall.sh
```
The Uninstallation script stops the Mobility Service, the sync agents, and the PostgreSQL database server. It also uninstalls all Mobility Service RPMs, drops the Mobility Service PostgreSQL database, and deletes the following directories and files from the Mobility server:
```
/opt/novell/datasync
/usr/sbin/gms (symbolic link)
/etc/datasync
/var/lib/datasync
/var/log/datasync
/var/run/datasync
/var/lib/pgsql
```