Notes for the upgrade from Nexus Professional 1.7.1 to 1.9.x

Installation

1. Download Nexus 1.9.0.2 from Sonatype

2. Review the notes from Sonatype regarding the upgrade (http://nexus.sonatype.org/upgrading-nexus.html).  Here is the relevant upgrade note:

Sonatype has changed how the lucene indexes are stored on disk,  it is required that users reindex all repositories in their nexus server to start benefitting from the changes (and for search to work properly).

3. Nexus 1.9.x requires Java 1.6 [NEXUS-3959].  Check that this is available on the system ( java -version )

4. Unzip Nexus to the /services/nexus directory.  There may be a warning about the file sonatype-work/README.txt being overwritten.  It is ok to overwrite this file.

# cd /services/nexus
# unzip nexus-professional-webapp-1.9.0.2-bundle.zip

5. Install the URL authentication realm jar version 2.2.1 and configuration file.

The jar file can be downloaded from central: http://repo2.maven.org/maven2/org/sonatype/security/realms/security-url-realm/2.2.1/security-url-realm-2.2.1.jar

Documentation is in the Sonatype wiki: https://docs.sonatype.com/display/SPRTNXOSS/URL+Realm

The configuration file is attached to this page as url-realm.xml

# cd /services/nexus
# cp security-url-realm-2.2.1.jar nexus-professional-webapp-1.9.0.2/runtime/apps/nexus/lib/
# cp url-realm.xml sonatype-work/nexus/conf

6. Activate the nexus-branding-plugin which displays the jboss.org logo

# cd /services/nexus
# cp -r nexus-professional-webapp-1.9.0.2/runtime/apps/nexus/optional-plugins/nexus-branding-plugin-1.9.0.2/ nexus-professional-webapp-1.9.0.2/runtime/apps/nexus/plugin-repository/

Make a backup of the default properties file

# cp nexus-professional-webapp-1.9.0.2/conf/plexus.properties nexus-professional-webapp-1.9.0.2/conf/plexus.properties.default

Add the following lines at the end of the file nexus-professional-webapp-1.9.0.2/conf/plexus.properties

# JBoss logo path used by the branding plugin

branding.image.path=${application-conf}/jbossorg_logo.png

7. Stop nexus and httpd

# service httpd stop
# service nexus stop

8. Remove the installed nexus-archetype-plugin since this is now included in the default nexus installation

# mv sonatype-work/nexus/plugin-repository/nexus-archetype-plugin-1.0.1 /tmp

9. Remove the installed nexus-audit-plugin because the required auditing features are now included in the default nexus install

# mv sonatype-work/nexus/plugin-repository/nexus-audit-plugin-1.5 /tmp

10.  Update the symlink to the nexus startup script

# cd /etc/init.d
# rm nexus
# ln -s /services/nexus/nexus-professional-webapp-1.9.0.2/bin/jsw/linux-x86-64/nexus nexus

11. Start the nexus server and Apache

# service nexus start
# service httpd start

Test

1. Open a browser and view the main page (https://repository.jboss.org/nexus).  Check that the page displays the correct version (1.9.0.2) in the upper right corner.
2. Log in to nexus with a valid JBoss.org username to verify the configuration of the URL realm.
   1. Click on "Repositories" and verify that the correct repositories are displayed. 
   2. Log out.
3. Log in with an admin account.
   1. Click on "Administration -> System Files" and view the nexus.log.  Check that there were no errors when starting the server.
   2. Click on "Administration ->Licensing" to verify that the license is correctly configured.
   3. Click on "Administration ->Plugin Console" and check that all the plugins show status "Activated"

Cleanup

If everything goes ok, and the new version of Nexus is working, some of the old directories can be cleaned up.

# rm -rf /tmp/nexus-archetype-plugin-1.0.1
# rm -rf /tmp/nexus-audit-plugin-1.5
# rm -rf /services/nexus/custom-app-configs

.