The following section describes how to migrate from an existing Nexus instance to a Nexus version that is compatible with a Talend product version 6.x or higher while keeping your configuration settings and the artifacts you have previously published to the repository.
For more information on the Nexus repository and how to use it with the Talend products, see the Talend Installation Guide.
Backing up the existing Nexus working directory
In the Nexus installation directory, the sonatype-work folder is the Nexus work directory which contains the Nexus configuration and data storage (repositories, settings, logs, published artifacts, etc.).
For more information on the different Nexus directories, read the Sonatype Nexus documentation.
To backup the existing Nexus data, make sure Nexus is shut down and copy the <OldNexusInstallationDirectory>/sonatype-work folder to the location of your choice.
Updating to the new Nexus instance
Inside the new Talend Administration Center application archive file, you will find the Artifact-RepositoryNexus-VA.B.C.D.E.zip file that contains the Nexus artifact repository.
Unzip and install the new Nexus instance, as described in the Talend Installation Guide.
Paste the backed up sonatype-work folder in the <NewNexusInstallationDirectory>/sonatype-work folder. When you start the new instance of Nexus it will read the existing repository configuration from the sonatype-work folder.
Executing the migration script
Inside the Artifact-RepositoryNexus-VA.B.C.D.E.zip archive file, you will also find the migration-A.B.C folder that contains the migration script as well as a .properties file that you can update in order to adapt the script to your Nexus repository.
Copy the <NewNexusInstallationDirectory>/migration-A.B.C folder to the location of your choice.
Open the following file and check that the Nexus URL and login connection information correspond to your Nexus instance. If not, update them and save your changes.
Browse to the migration-A.B.C folder and execute the following command:
java -jar <nexus-migration-A.B.C.jar>
<nexus-migration-A.B.C.jar>corresponds to the .jar file name that is in the migration-A.B.C folder.
The new Nexus configuration will be merged with your existing data at next start-up.
(Optional) For users who use HTTPS protocol to access their Nexus instance without a known certificate
If you already have a Nexus instance with an SSL certificate that is not recognized in your Java environment, you need to do the following.
Download the certificate from the Nexus server:
openssl s_client -connect <server>:<port> -showcerts > myserver_cert
Install it into the Java instance used to launch the migration tool:
keytool -importcert -trustcacerts -file myserver_cert -alias ca_alias -keystore "<JRE_HOME>\lib\security\cacerts"