2.19 Upgrading Nitro Web Services (RPM)

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

2.19.1 Upgrade Steps

Do the following:

• 2.19.2 Upgrade to MongoDB 3.2.x, if you are upgrading Nitro Web Services from a version prior to 2.1.0
• 2.19.3 Back up the MongoDB Databases, if you are upgrading Nitro Web Services from version 2.1.0 or later
• 2.19.4 Upgrade Nitro Web Services
• 2.19.5 Grant Users Nitro Permissions in Viewpoint

2.19.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:

1. Check your MongoDB server version.

   [root]# rpm -qa | grep mongo

2. If the MongoDB server version is older than 3.2.x, then you will need to upgrade the databases. See 2.20 Upgrading to MongoDB 3.2.x (RPM) for more information.

2.19.3 Back up the MongoDB Databases

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

1. Stop all services that are using the MongoDB databases.
2. Back up the MongoDB databases.

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

3. Restart the services.

2.19.4 Upgrade Nitro Web Services

On the Nitro Web Services Host, do the following:

1. 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 2.13 Preparing for RPM Installation or Upgrade.
2. If you are upgrading Nitro Web Services from a version prior to 2.1.0, confirm the MongoDB database is upgraded to 3.2.x. See 2.20 Upgrading to MongoDB 3.2.x (RPM) for more information.
3. Stop the services.

   • Red Hat 6-based systems

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

   • Red Hat 7-based or SUSE 12-based systems

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

4. If you are upgrading Nitro Web Services from version 2.1.0 or later, do the following on the Nitro Web Services MongoDB host.
   1. Stop all services on the host.
   2. Back up the Nitro Web Service MongoDB database.

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

   3. Restart the services.
5. Install the upgrade.

   • Red Hat 6-based or Red Hat 7-based systems

     [root]# yum update nitro-web-services

   • SUSE 12-based systems

     [root]# zypper update nitro-web-services

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

   • Red Hat 6-based systems

     [root]# chkconfig nitro-web-services on
     [root]# chkconfig nitro-zmq-job-status-adapter restart

   • Red Hat 7-based or SUSE 12-based systems

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

7. Merge any customizations from the nitro.cfg and the zmq_job_status_adapter.cfg files (and any other files) you backed up earlier in this procedure into the new files.
   

   See the steps in 2.7.3 Install and Configure Nitro Web Services for more information on the configuration files.

8. Start the services.

   • Red Hat 6-based systems

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

   • Red Hat 7-based or SUSE 12-based systems

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

2.19.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.

© 2017 Adaptive Computing