You are here: Manual Installation > Upgrading > Nitro Integration > Upgrading Nitro Web Services

2.27 Upgrading Nitro Web Services

This topic contains instructions on how to upgrade Nitro Web Services.

2.27.1 Upgrade Nitro Web Services

On the Nitro Web Services Host, do the following:

If you have not already done so, complete the steps to prepare the host. See 2.8 Preparing for Nitro Manual Installation for more information.
If you are upgrading Nitro Web Services from a version prior to 9.1.0, confirm the MongoDB database is upgraded to 3.2.x. See 2.19 Upgrading to MongoDB 3.2.x for more information.

Stop the services.

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

Back up the contents of the /opt/nitro-web-services/etc directory (contains the nitro.cfg and the zmq_job_status_adapter.cfg files).
Remove the /opt/nitro-web-services directory.
```
[root]# rm -rf /opt/nitro-web-services
```
Change the directory to the root of the unpacked Nitro tarball bundle.
```
[root]# cd nitro-tarball-bundle-<version>-<OS>
```
Create the /opt/nitro-web-services directory.
```
[root]# mkdir -p /opt/nitro-web-services
```
Identify the Nitro Web Services tarball (nitro-web-services-<version>-<OS>.tar.gz) and unpack the tarball into /opt/nitro-web-services.
```
[root]# tar -xzvpf  nitro-web-services-<version>-<OS>.tar.gz -C /opt/nitro-web-services --strip-components=1
```
Install Nitro Web Services. This step assumes the installation directory is /opt/nitro-web-services.
```
[root]# cd /opt/nitro-web-services
[root]# ./install.sh
```
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 "Understand and edit the configuration files. This includes clarifying what each configuration file is for and what to expect the first time the NWS service is started vs. each subsequent start.The nitro_user with dbOwner permissions was set up earlier in the procedure (see Install MongoDB).When you first start nitro-web-services, the nitro-db Mongo database (including its collections and indexes) is created. The nitro-db 'user' collection is also populated with the default Nitro Web Services API users/passwords. Several of the options defined in the configuration files influence this process.Usernames and passwords are created only if they do not yet exist. Changing a password in the configuration file after initial startup will not update the password.The installation provides two configuration files:/opt/nitro-web-services/etc/nitro.cfgThis is the Nitro Web Services web application configuration file.Before initial startup, set the db_password to be the nitro_user password. It is also recommended that you change all other default passwords before starting Nitro Web Services. If you do not change the passwords at this point, it will be more difficult to change them later.By default, NWS uses an auto-generated self-signed SSL certificate to encrypt the link between the web server and the browser clients. The auto-generated self-signed SSL certificate is created at service start up; not during the installation process.However, you can use your own certfile, keyfile, and ca_certs files if you wish. If you choose to use your own ssl_certfile and ssl_keyfile, ssl_create_self_signed_cert=true is ignored.By default, NWS does not encrypt network traffic with MongoDB. You set the db_ssl_* properties if you choose to enable TLS/SSL when installing MongoDB earlier in this topic./opt/nitro-web-services/etc/zmq_job_status_adapter.cfgThis is the Nitro ZMQ Job Status Adapter configuration file.The Nitro ZMQ Job Status Adapter listens to job status updates on the ZMQ bus and publishes them to MongoDB using the Nitro Web Services REST API. The username and password must be set to a Nitro Web Services API user with write permissions. At minimum, set the password for nitro-writeonly-user to the password defined in /opt/nitro-web-services/etc/nitro.cfg and make sure the SSL options are set correctly based on SSL settings in /opt/nitro-web-services/etc/nitro.cfg." for more information on the configuration file.

Restart the services.

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

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