X

Help Articles are product support tips and information straight from the NV5 Geospatial Technical Support team developed to help you use our products to their fullest potential.



829 Rate this article:
No rating

How to manually update the Node.js or MongoDB packages used by the Next-Generation License Server

In some cases, you may need to update the version of MongoDB or Node.js that are installed alongside and used with the Next-Generation License Server, for security vulnerability concerns or otherwise. These packages can be manually updated with minimal risk as long as you keep with the exact same major AND minor version of the products included with the Next-Generation License Server.
 

License Server version Default MongoDB version Default Node.js version
4.1 5.0.15 16.19.1
4.2.1 6.0.9 18.18.2
4.3 6.0.16 18.20.4

 

WARNING: Alternative versions of MongoDB and Node.js have not been fully tested for compatibility with the License Server, but they should work as long as the specific versioning guidelines below are followed. Proceed at your own risk!

 

Updating MongoDB 

  1. First determine which version of MongoDB is used by the License Server version you have installed. This can be found in the installation guide under "System Requirements" (Linux | Windows). For example, the Linux documentation mentions that "...the License Server requires an Intel/AMD 64-bit processor and a Linux distribution. In general, the License Server should successfully function on the Linux systems supported by MongoDB Community Server 6.0 and Node.js 18." So in this case, you will need to make sure you stay with mainline MongoDB version 6.0. Make sure to verify which version you need before proceeding! 
  2. With that versioning in mind, MongoDB Community Edition can be downloaded here: https://www.mongodb.com/try/download/community. In addition to downloading the correct version for the correct platform, make sure also to get the "server" package version (this dropdown is only there for Linux). 
  3. Before installing the updated MongoDB, stop the Next-Generation License Server service. 
    1. Linux: 
      sudo INSTALL_DIR/node/bin/node INSTALL_DIR/service.js stop
      
    2. Windows: Open Windows Service panel, then right-click the NV5 Geospatial License Server service and select Stop.
       
  4. After installing the new MongoDB version, restart the Next-Generation License Server service.
    1. Linux:
      sudo INSTALL_DIR/node/bin/node INSTALL_DIR/service.js start
    2. Windows: Open Windows Services panel, then right-click the NV5 Geospatial License Server service and select Start.

 

Updating Node.js

  1. First determine which version of Node.js is used by the License Server version you have installed. This can be found in the installation guide under "System Requirements" (Linux | Windows)For example, the Linux documentation mentions that "...the License Server requires an Intel/AMD 64-bit processor and a Linux distribution. In general, the License Server should successfully function on the Linux systems supported by MongoDB Community Server 6.0 and Node.js 18." So in this case, you will need to make sure you stay with mainline Node version 18. Make sure to verify which version you need before proceeding! 
  2. With that versioning in mind, Node.js can be downloaded here: https://nodejs.org/dist/. You can download a standalone installer or use a package manager. 
  3. Before installing the updated Node.js package, stop the Next-Generation License Server service.
    1. Linux: 
      sudo INSTALL_DIR/node/bin/node INSTALL_DIR/service.js stop
      
    2. Windows: Open Windows Service panel, then right-click the NV5 Geospatial License Server service and select Stop.
       
  4. After installing the new Node.js version, restart the Next-Generation License Server service.
    1. Linux:
      sudo INSTALL_DIR/node/bin/node INSTALL_DIR/service.js start
    2. Windows: Open Windows Services panel, then right-click the NV5 Geospatial License Server service and select Start.

 

 

 

 

 

 

Created by BC-US 6/10/2024 | Reviewed by TS 6/11/2024

Please login or register to post comments.
Featured

End-of-Life Policy Enforcement for ENVI 5.3 / IDL 8.5 and Earlier Versions

5/6/2024

April 1, 2024 Dear ENVI/IDL Customer,  We are reaching out to notify you of our supported... more »

How to Upgrade licenses to ENVI 6.x / IDL 9.x

12/5/2023

What is the new Upgrade function? Starting with ENVI 6.0 and IDL 9.0, we have implemented an... more »

What to do if the 'License Administrator - License Server' for the Next-Generation License Server does not start?

6/13/2023

Background: With the release of ENVI 5.7 & IDL 8.9 and the corresponding Next-Generation licensing... more »

Next-Generation Licensing FAQ

4/28/2023

  NV5 Geospatial has adopted a new licensing technology for all future releases of our ENVI, IDL... more »

The IDL Virtual Machine

6/6/2013

What is the IDL Virtual Machine? An IDL Virtual Machine is a runtime version of IDL that can... more »