Before you upgrade the vRealize Code Stream appliance, you must migrate your artifacts from the embedded Artifactory repository to an external Artifactory instance. To migrate your artifacts, you must understand the services used to migrate them, and perform several steps. You can then migrate your Artifactory endpoint, and upgrade the appliance.

About this task

jFrog Artifactory provides import and export services to migrate metadata and artifacts in two ways.

  • System level migration. Export and import the entire Artifactory server, including configuration, security information, stored data, and metadata. The format used is identical to the system backup format.

  • Repository level migration. Export and import data and metadata that is stored in a repository.

Prerequisites

  • To import and export Artifactory data and settings to an external Artifactory server, review the instructions. See Artifactory Import and Export.

  • To export your artifacts and metadata, familiarize yourself with the folder structures used in the system level migration and the repository level migration.

Caution:

Before you migrate your artifacts, back them up. The upgrade, which you perform after you migrate your artifacts, removes all artifacts that existed in the embedded Artifactory before the upgrade.

Procedure

  1. Log in to your virtual appliance as a normal user.
  2. Delete the files named /etc/opt/jfrog/artifactory/plugins/vcac-plugin.groovy, remote-list-browsing.groovy, and vcac-plugin.xml from your embedded instance of Artifactory.
  3. In the embedded Artifactory instance, select the approach to migrate your embedded Artifactory data to an external Artifactory instance, and review the folder structure.

    Option

    Description

    Repository-level migration

    Folders include builds, etc, licenses, and repositories.

    Files include the XML file named artifactory.config, a properties file named artifactory.properties, and the XML file named security.

    System-level migration

    Folders include username and username.artifactory-metadata.

  4. If vRealize Code Stream cannot export the data because the target destination does not have the correct permissions, run the following steps.
    1. Establish an SSH connection to the virtual appliance as a root user.

      For example: ssh root@VRCS_APPLIANCE

    2. Create a folder on the vRealize Code Stream appliance.

      For example: mkdir /var/temp/artifactory

    3. Assign ownership to the user named artifactory on the target folder.

      For example: chown –r artifactory:artifactory /var/temp/artifactory

    4. In the Artifactory Import & Export tool, click Export, and enter the name of the folder that you created.

    After the export, you can use ftp, winscp, or another tool to move the exported files to another instance or to an external Artifactory server.

Results

You have migrated your artifacts from the embedded Artifactory repository to an external Artifactory instance. For more information about the procedure to migrate your Artifactory data, see the jFrog documentation at https://www.jfrog.com.

What to do next

Prepare to upgrade your instance of vRealize Automation. See Downloading vRealize Automation Appliance Updates.