Upgrading NetX on Linux

NetX provides an upgrade pack for Linux that can be used to create a new installation or to upgrade your existing installation.

Before you begin

Question Answer
Which version are you upgrading from?

If you are upgrading from a version prior to NetX 9, you must perform additional steps before completing this tutorial:

After completing the process outlined in Upgrading to Solr 7 on Windows, you can return to this article to finish the NetX upgrade process.

Are you running NetX in a distributed configuration? When upgrading multiple server instances, all server nodes should first be shut down. Each node should be upgraded in succession. Only once the first node has started up completely should the other nodes be started. This is because the application may be in the middle of database schema changes that need to complete before other nodes start using the database.
Have you backed your NetX instance? See Backing Up NetX for more details. 
Are you using supported software to host the latest version of NetX? Please review Supported Platforms to verify that your environment is supported for the latest release of NetX.
Have you reviewed the release notes? Occasionally, functionality is changed or removed in new releases. Make sure your users are familiar with the changes the upgrade will bring and re-train if necessary.

Upgrading NetX

  1. Download the latest NetX upgrade pack from our Service Portal.
  2. Shut down Tomcat. In the example below, we also tail the catalina.out log to see when the process has terminated:

    sudo /opt/netx/bin/shutdown.sh; tail -f /opt/netx/logs/catalina.out
  3. Once Tomcat has shut down, unzip the pack into the NetX application folder, overwriting the existing contents:

    $ sudo unzip -o ~/NetX-App-Complete-9.0.0-master.zip -d /opt/netx/
  4. Make the Tomcat scripts executable:

    sudo chmod +x /opt/netx/bin/*.sh

Upgrading the Solr core

If you are upgrading from a version older than 9.x, and have already followed the instructions in  Upgrading to Solr 7 on Linux , please skip to Verifying the upgrade.

Each time that you upgrade NetX, you will need to copy the new version of the Solr core into your Solr application folder. In the examples below, Solr runs as a service, and the solr user has read access to the /opt/netx/solr-cores/7/netx directory. Your environment may vary.

  1. Stop the Solr application:

    service solr stop

     

  2. Copy the Solr core from the NetX application folder into the Solr folder.

    sudo -u solr cp -a /opt/netx/solr-cores/7/netx /var/solr/data/
  3. Start Solr:

    service solr start

Starting NetX

After the NetX application files have been upgraded, the new Solr core copied over and the Solr service started, it's finally time to start the Tomcat server.  In the example below, we also tail catalina.out to see when it has fully started and the application is ready to use.

sudo /opt/netx/bin/startup.sh; tail -f /opt/netx/logs/catalina.out

Some NetX upgrades include database schema changes that may take a long time to complete on your server. When you see the log entries shown below appear in catalina.out, it's safe to assume that the core upgrade process (version control) has completed. DO NOT restart your server or kill the NetX process before you see these entries appear, or you may risk a corrupt installation or database state.

If you'd like to watch the progress of version control, you can tail the main application log here: /opt/netx/logs/exogen.log.

Wed Dec 04 12:15:38 PST 2019 EXOGEN INFO: Event channels started: category
Wed Dec 04 12:15:38 PST 2019 EXOGEN INFO: Event channels started: asset
Wed Dec 04 12:15:38 PST 2019 EXOGEN INFO: Event channels started: view
Wed Dec 04 12:15:38 PST 2019 EXOGEN INFO: Event channels started: constituent
Wed Dec 04 12:15:38 PST 2019 EXOGEN INFO: Event channels started: version
Wed Dec 04 12:15:38 PST 2019 EXOGEN INFO: Event channels started: glacier
Wed Dec 04 12:15:38 PST 2019 EXOGEN INFO: Event channels started: cache
Wed Dec 04 12:15:38 PST 2019 EXOGEN INFO: Event channels started: user
Wed Dec 04 12:15:38 PST 2019 EXOGEN INFO: Event channels started: clock
Wed Dec 04 12:15:38 PST 2019 EXOGEN INFO: Event channels started: statistics
Wed Dec 04 12:15:38 PST 2019 EXOGEN INFO: Event channels started: dataset
Wed Dec 04 12:15:38 PST 2019 EXOGEN INFO: Event channels started: system
Wed Dec 04 12:15:38 PST 2019 EXOGEN INFO: Event channels started: websocket
Wed Dec 04 12:15:38 PST 2019 EXOGEN INFO: Event channels started: view_metadata
Wed Dec 04 12:15:38 PST 2019 EXOGEN INFO: XMP engine: EXIFTOOL
Wed Dec 04 12:15:38 PST 2019 EXOGEN INFO: Event channels started.
Wed Dec 04 12:15:38 PST 2019 EXOGEN INFO: Guava services started.
Wed Dec 04 12:15:38 PST 2019 EXOGEN INFO: Database batch updater started.

Verifying the upgrade

  • Verify that assets and thumbnails are available.
  • Log into NetX, go to System > Overview, and check the Application Version. The application version should match the new version that was listed in the installer wizard.
  • Reindexing is often recommended after an upgrade. Some upgrades (such as new Solr versions or schema changes) will automatically begin a site-wide reindex as part of the upgrade process. If this reindex is interrupted via server restart or some other process, you must restart it manually before assets will appear. For more information on how to perform a reindex, and how to check if a reindex is running on your site, see Rebuilding the Search Index.
Was this article helpful?
0 out of 0 found this helpful