This instructions are applicable if you are already running Nexus Repository Manager 3.1.0 or newer installed or upgraded using specific instructions.
If you are upgrading from a version earlier than 3.1.0, please use the alternate instructions for upgrade.
Become familiar with the basic directory structure of a Nexus Repository Manager installation. You are encouraged to stick with the standard installation layout to make future upgrades as simple as possible.
You will have to determine your existing installation data directory location. Record this value for later use.
Download the Latest Installer Archive
Download the latest installer archive for your platform from the official downloads.
Extract the newest downloaded distribution archive using the standard approach.
Preparing the new Install
The archive distribution offers the familiar process of downloading and simply extracting the install archive in place. There is no graphical or automated process and all commands are done inside a terminal console.
These examples use 3.2.0-01 as the new version.
tar xzvf nexus-3.2.0-01-mac.tgz tar xzvf nexus-3.2.0-01-unix.tar.gz 7za.exe nexus-3.2.0-01-win64.zip
nexus-3.2.0-01/bin/nexus.vmoptions file with your existing version.
If you changed the default location of the Data Directory, then edit
./bin/nexus.vmoptions and change the line
-Dkaraf.data=../sonatype-work/nexus3 to point to your existing data directory. Example:
If you changed the default location of the temporary directory, then edit
./bin/nexus.vmoptions and replace the line
-Djava.io.tmpdir=../sonatype-work/nexus3/tmp to point to your preferred temporary directory.
If you adjusted the default Java virtual machine max heap memory, then edit
./bin/nexus.vmoptions and edit the line
If you have enabled jetty HTTPS access, make sure your
etc/jetty/jetty-https.xml SSL keystore location is still available to the new install.
If you manually adjusted any other install files under
./etc you will need to manually perform a diff between the old files and the new files and apply your changes if applicable to the new version.
Perform the Upgrade
- Ensure you have taken recent backups of the existing Data Directory and any custom blobstore locations according to our recommended practices. Because of involved Upgrade steps, downgrading a NXRM version is not supported and will almost always result in failures. If you have issues, restore from this backup instead.
- Stop your existing install using the scripts under
./binor your operating system service. Make sure it stops completely.
- Start the new installation using the scripts under
./binor adjust your operating system service to use these scripts.
- Review the log files for any possible issues and sign-in to the server to confirm things are working as expected.