You are here: RPM Installation > Upgrading > Upgrading Nitro Web Services (RPM)

3.35 Upgrading Nitro Web Services (RPM)

This topic contains instructions on how to upgrade Nitro Web Services using the RPM upgrade method.

3.35.1 Upgrade Steps

Do the following:

3.35.2 Upgrade to MongoDB 3.2.x, if you are upgrading Nitro Web Services from a version prior to 2.1.0
3.35.3 Back up the MongoDB Databases, if you are upgrading Nitro Web Services from version 2.1.0 or later
3.35.4 Upgrade Nitro Web Services
3.35.5 Grant Users Nitro Permissions in Viewpoint

3.35.2 Upgrade to MongoDB 3.2.x

Beginning with version 2.1.0, Nitro Web Services requires MongoDB 3.2.x.

On the Nitro Web Services MongoDB host, do the following:

Check your MongoDB server version.
```
[root]# rpm -qa | grep mongo
```
If the MongoDB server version is older than 3.2.x, then you will need to upgrade the databases. See 3.25 Upgrading to MongoDB 3.2.x (RPM) for more information.

3.35.3 Back up the MongoDB Databases

This procedure is only applicable if you did not have to upgrade the MongoDB databases earlier in this topic. See 3.35.2 Upgrade to MongoDB 3.2.x for more information.

On the Nitro Web Services MongoDB host, do the following:

Stop all services that are using the MongoDB databases.

Back up the MongoDB databases.

[root]# cd /root
[root]# mongodump -u admin_user -p secret1

Restart the services.

3.35.4 Upgrade Nitro Web Services

On the Nitro Web Services Host, do the following:

If you installed Nitro Web Services on its own host or if Nitro Web Services is the first component being upgraded on a host with other RPM installations, complete the steps to prepare the host. See 3.21 Preparing for RPM Upgrades for more information.

Stop the services.

[root]# systemctl stop nitro-web-services.service
[root]# systemctl stop nitro-zmq-job-status-adapter.service

Install the upgrade.

[root]# zypper update nitro-web-services

If you are upgrading Nitro Web Services from 2.0.0, re-enable the services.

[root]# systemctl enable nitro-web-services.service
[root]# systemctl enable nitro-zmq-job-status-adapter.service

If you have customized your configuration files, the RPM upgrade will have copied the new configuration files into the /opt/nitro-web-services/etc directory with a .rpmnew extension. Merge any parameter changes in the .rpmnew files into the respective configuration files.
See the steps in 3.16.3 Install and Configure Nitro Web Services for more information on the configuration files.

Restart the services.

[root]# systemctl start nitro-web-services.service
[root]# systemctl start nitro-zmq-job-status-adapter.service

3.35.5 Grant Users Nitro Permissions in Viewpoint

Verify that the users who work with Nitro Web Services have the appropriate role in their Viewpoint user principal.

These are the Viewpoint roles for Nitro:

NitroAdmin – Administrative user, with permission to create Nitro application templates and manage other user's Nitro jobs.
NitroUser – Basic user, with permission to create and manage their own Nitro jobs.

See Creating or Editing Principals in the Moab Viewpoint Reference Guide for instructions on setting up principals.