4.1 Updating to GroupWise Mobility Service 2014 R2

The update process pertains to either the following types of updates:

Any version of GroupWise Mobility Service to GroupWise Mobility Service 2014 R2.
Any version of the Novell Data Synchronizer Mobility Pack to GroupWise Mobility Service 2014 R2.

Complete the following steps to update to GroupWise Mobility Service 2014 R2:

4.1.1 Obtaining the GroupWise Mobility Service 2014 R2 ISO

You can obtain the GroupWise Mobility Service 2014 R2 ISO from these locations:

Novell Customer Center

Log in to the Novell Customer Center.
In the Organization drop-down list (next to your name in the upper-right corner), select your organization that is entitled to GroupWise Mobility Service.
Click Software.
In the GroupWise section, locate GroupWise Mobility Service 2014 R2, then click to display the download page.
Follow the online instructions to download the GroupWise Mobility Service ISO and the GMSsslCheck.tar file to a convenient temporary directory on the Mobility server.
```
novell-groupwise-mobility-service-14.2.0-x86_64-build_number.iso
```
Continue to Running GMSsslCheck.

Novell Downloads Website

On Novell Downloads, under Patches, click Search Patches to display Patch Finder.
In the Select a Product drop-down list, select GroupWise.
At the bottom of the GroupWise product list, click GroupWise Mobility Service 2014 R2 to list the available patches.
Click GroupWise Mobility Service 14.2.0, review the product description, then click Proceed to Download.
Follow the online instructions to download the GroupWise Mobility Service ISO and the GMSsslCheck.tar file to a convenient temporary directory on the Mobility server.
```
novell-groupwise-mobility-service-14.2.0-x86_64-build_number.iso
```

4.1.2 Running GMSsslCheck

NOTE:This only needs to be run if you upgrading from Mobility 2.1 or earlier.

Before you upgrade your Mobility system, the GMSsslCheck utility needs to be run to ensure that the SSL settings on your GroupWise POA servers matches the setting in Mobility. Mobility no longer fails over between SSL and non SSL when communicating with the POAs. Follow the steps below to run the utility:

Open a terminal and extract the content of the GMSsslCheck.tar file to a temporary location on your GMS server using the following command:
```
tar xvf GMSsslCheck.tar
```
In the terminal, browse to the folder where you extracted the files.
Run the following command to launch the utility:
```
python sslcheck.pyc
```
In the menu prompt, select option 1.

The tool connects to all of your GroupWise POAs and checks their SSL settings against the GMS settings. If the settings do not match those in GMS, the information is displayed so you can resolve the settings.
Continue with Upgrading GroupWise Mobility Service

4.1.3 Upgrading GroupWise Mobility Service

Upgrading Mobility on SLES 11

The update process includes installing the GroupWise Mobility Service 2014 R2 ISO file, and then running the Update script:

Using Patch CD Update in YaST

If you are updating from the Novell Data Synchronizer Mobility Pack, stop the Synchronizer services and verify that they have stopped:
```
rcdatasync stop
ps -eaf | grep datasync
```
or

If you are updating from a previous version of GroupWise Mobility Service, stop the Mobility Service and verify that it has stopped:
```
rcgms stop
rcgms status
```
Ensure that you know the location where the Mobility Service ISO was downloaded on the Mobility server.
On your Linux desktop, click Computer > YaST to open the YaST Control Center.
Enter the root password.
Under Groups, click Software, then click Patch CD Update.

NOTE:The Patch CD Update process pulls all updates in the channels that you have selected. This might include updates in addition to the GroupWise Mobility Service.
Click Next to start the update.
On the Media Types page, select Local ISO Image, then click Next.
In the Repository Name field, specify a name for the repository that will hold the Mobility Service software, such as Mobility Service.
In the Path to ISO Image field, specify the full path name of the ISO file from Step 1, then click Next.
Accept the License Agreement, then click Next.
On the Migration Repositories page, click Next.
On the Distribution Upgrade Settings page, click Next.
In the Confirm Update dialog box, click Start Update.
On the Installation Completed page, click Finish.

You do not need to restart the server after the update.
Continue with Running the Mobility Service Update Script.

Running the Mobility Service Update Script

Running the Update script updates the Mobility Service database for use with the updated software.

NOTE:The process of updating to GroupWise Mobility Service 2014 R2 from versions of the Data Synchronizer Mobility Pack earlier than 1.2.5 might take longer than previous Mobility Pack updates. It is not unusual for the Update script to run for over an hour for a large database.

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
```
Ensure that PostgreSQL is running:
```
rcpostgresql status
```
Run the Mobility Service Update script:
1. Enter the following command:
```
./update.sh
```
  You are prompted to confirm the update:
```
The update process may take some time. During this process, the GroupWise Mobility Service will be shut down. Are you sure you want to update the GroupWise Mobility Service now?
```
2. Enter yes to start the update.
  
  The Update script prompts you:
```
Reset logging level for all GroupWise Mobility Services to Info?
```
  The Info logging level provides sufficient logging for a typical Mobility system. If you have set the logging level to Debug in an earlier version, you can now set it to Info and still get the logging you need to manage your Mobility system.
  
  IMPORTANT:Info is the default logging level and is strongly recommended because it balances the amount of data logged, the amount of disk space required for log files, and the load on the Mobility system.
  
  For more information about logging levels, see Working with Log Files in the GroupWise Mobility Service 2014 R2 Administration Guide.
3. Enter yes to reset the logging level to Info for the GroupWise Mobility Service.
  
  The Update script prompts you:
```
Enable anonymous information to be automatically sent to Micro Focus to improve your GroupWise mobile experience?
```
  You can contribute to the gathering of anonymous usage data about your Mobility system to help improve the GroupWise Mobility Service product. For more information, see Providing Anonymous Feedback about Your Mobility System in the GroupWise Mobility Service 2014 R2 Administration Guide.
4. (Optional) Enter yes to participate in the gathering of anonymous feedback.
  
  The Update script now shuts down the Mobility Service, updates the Mobility Service database, then restarts the Mobility Service.
  
  For some version updates, the update process finishes quickly. However, the update process can take longer for a large database.
  
  WARNING:Do not cancel this process, even if it takes a very long time. Cancelling the process before it finishes can cause damage to the Mobility Service database.
  
  When the Update script finishes, your updated Mobility system is ready for use.
  
  NOTE:The process of updating to GroupWise Mobility Service 2014 R2 from versions of the Data Synchronizer Mobility Pack earlier than 1.2.5 might take longer than previous Mobility Pack updates. It is not unusual for the Update script to run for over an hour for a large database.
Continue with Checking the Status of the Mobility Service after Update.

Upgrading Mobility on SLES 12

Before upgrading Mobility, the new ISO must be downloaded to the server.

In a terminal, mount the GroupWise Mobility ISO using the following command:
```
mount -o loop <path to the Mobility ISO> /mnt
```
Browse to /mnt and run the install.sh.
Follow the prompts to upgrade Mobility.

Upgrading from SLES 11 to SLES 12

Before you can upgrade from SLES 11 to SLES 12, the following prerequisites must be met:

GMS 14.2.1 HP1 must be installed on the SLES 11 server before the upgrade to SLES 12.
The SLES 11 server must be registered with NCC.
You must be updating to SLES 12 SP1 or later.
You must have the GMS 14.2.1 HP1 or later iso to use for the upgrade after upgrading to SLES 12.

To upgrade the server from SLES 11 to SLES 12, do the following:

Run /opt/novell/datasync/tools/pgUpdate.sh to update postgresql. This can be done at any time before upgrading the OS.
Upgrade the OS to SLES 12.

NOTE:As part of the upgrade, the Mobility server files may be removed. This does not affect the Mobility data.
In a terminal, mount the GroupWise Mobility ISO for SLES 12 using the following command:
```
mount -o loop <path to the Mobility ISO> /mnt
```
Browse to /mnt and run the install.sh.
Follow the prompts to upgrade Mobility.

4.1.4 Checking the Status of the Mobility Service after Update

The Mobility Service Update script starts the Mobility Service for you. If the update 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:
```
rcgms status
```
Use the following commands to manually start and stop the Mobility Service:
```
rcgms start
rcgms restart
rcgms stop
```

4.1.5 Changing the User Source for Your Mobility System (Optional)

For background information about the user source alternatives, see Selecting the User Source for Your Mobility System. For usage instructions, see Changing between LDAP and GroupWise as the User Source in the GroupWise Mobility Service 2014 R2 Administration Guide.

The Data Synchronizer Mobility Pack created a Synchronizer system based on LDAP as the user source for user provisioning and, optionally, for device authentication. In Synchronizer Web Admin, the Authentication Type setting on the Mobility Connector Settings page set the device authentication method for your Synchronizer system. This setting automatically transferred to the Authentication setting on the User Source page in the Mobility Admin console.

IMPORTANT:If you are comfortable with the configuration that you used for your Synchronizer system, there is no need to change it for your Mobility system.

If you want to start using GroupWise as the user source for provisioning, new mobile device users are added to your Mobility system based on their GroupWise location (user_name.post_office_domain). Existing mobile device users are still associated with their LDAP context (cn=user_name,ou=organizational_unit,org=organization). On the Users page, you can determine the source of each user by mousing over it.

There is no direct way to change an existing user from being associated with LDAP to being associated with GroupWise. If it is important for you to do this, you must delete the user as an LDAP user, and then add the user as a GroupWise user. After this occurs, the best practice for data integrity is to have the mobile device user delete and re-add the email account on the device.

There is also no direct way to change from using an LDAP group to using a GroupWise group (distribution list in older GroupWise systems). As with individual users, you must delete the LDAP group from your Mobility system (which deletes all the LDAP users in the LDAP group), and then add the GroupWise group (which adds all the users based on the GroupWise group). Again, the affected users should delete and re-add their email accounts on their devices.

You might want to accomplish this transition over time, a few users at a time. If you want to accomplish the transition all at once, you can create a new Mobility system, based entirely on GroupWise provisioning and ion, and then switch from the old system to the new system, perhaps over night, without notifying your mobile device users. Most users will likely not notice the change. You can then have those users that contact you about data integrity issues delete and re-add their email accounts in order to resynchronize the GroupWise data.