Search


Cloud customer?
Upgrade in MyJFrog >


Working with an older version?

JFrog Artifactory 6.x
JFrog Xray 2.x
JFrog Mission Control 3.x
JFrog Distribution 1.x
JFrog Enterprise+ (Pre-Platform Release)




Overview

The procedure to upgrade Artifactory depends on your installation type. We strongly recommend reading through this page before proceeding with your upgrade.

Upgrading to version 7.x for the first time?

It is recommended that you first review what's new with the latest JFrog Platform. Review the breaking changes, deprecated features and more.

System Requirements

Before upgrading Artifactory please refer to System Requirements for information on supported platforms, supported browsers and other requirements. To learn about the HA architecture, refer to System Architecture.

Note: Make sure to use the same upgrade method (RPM, Debian, Docker, etc.) as the one you initially used to install Artifactory.

Before You Proceed

To ensure you can restore your Artifactory and database in case you encounter any issues during the upgrade process, we strongly recommend that you make sure your system and database backups are up to date.

Oracle Database users

Artifactory 7.x requires a new setup to connect to an Oracle Database. Refer to the Configure Artifactory to use Oracle for more information. 

Do you have more than one Artifactory instances connect to your single Xray instance?

When upgrading to the JFrog Platform, Xray must be connected only to a single Artifactory instance. If you have one Xray instance connected to more than one Artifactory instances, use one of the following options before proceeding with any upgrade: 

Option 1 (recommended): Keep one connected Artifactory instance to your single Xray instance, and upgrade the rest to version 7.x with newly installed Xray version 3.x instances. This option will require re-indexing the the additional Artifactory instances, and will cause some loss of configuration data. Learn More >

Option 2: Install additional Xray version 2.x instances for each Artifactory instance that you have, and restore all MongoDB and PostgreSQL data. Continue to upgrade each Artifactory and Xray pairs to version 7.x and version 3.x. This procedure is only suggested if you must keep all your Xray configurations and easily reconfigure them in the new instances. Learn More >

Installation Types

The install type is referenced as <type> in the different installation instructions below.

Subscription TypeInstall TypeDownload the Package
Pro
Pro X
Enterprise
Enterprise+
proDownload Link
Artifactory OSS
ossDownload Link
Artifactory CE
cpp-ceDownload Link
JFrog Container Registry
jcrDownload Link

Upgrade Steps

The upgrade procedure involves the following main steps:

  1. Download the package to upgrade (Linux Archive, RPM, Debian, Docker Compose, Helm).
  2. Stop the current server
  3. Extract/Install the package according to the installer distribution type.
  4. Check the Migration Log and review system.yaml to validate the migration was successful (only for upgrading from v6.x).
  5. Start the service using the start scripts or OS service management.
  6. Check the Artifactory Log for the status of the service.

Default Home Directory / $JFROG_HOME

The default Artifactory home directory is defined according to the installation type. For additional details see the Product Directory Structure page.

Note: This guide uses $JFROG_HOME to represent the JFrog root directory containing the deployed product, the home directory for all JFrog products.

Page Contents


Upgrading from Version Below 6.10

To upgrade from a version below 6.10.x, you first need to upgrade to version 6.10.x as described in the Upgrading Artifactory 6.x documentation, and then continue to upgrading from version 6.10 to 7.x.


Upgrading from Version 6.10.x to 7.x

Upgrading from JFrog Artifactory 6.18

To upgrade to Artifactory 7.x from version 6.18, you will need to upgrade to Artifactory 7.3.0 or to a higher version.

There are several new concepts introduced in Artifactory 7.x, improving the installation and customization process.

The following upgrade methods are supported:

Linux Archive Upgrade

Migration is a manual process for a Linux archive installation. The below steps also include copying directories over and running the migration script

Make sure to run all commands on the server with the user that's running Artifactory.

  1. Stop the current server.

    cd $ARTIFACTORY_HOME/bin
    ./artifactoryctl stop
  2. Extract the contents of the compressed archive and move it into artifactory directory.

    tar -xvf jfrog-artifactory-<pro|oss|cpp-ce>-<version>-linux.tar.gz
    mkdir jfrog
    mv jfrog-artifactory-<pro|oss|cpp-ce>-<version>-linux jfrog/artifactory
  3. Set your ARTIFACTORY_HOME and JFROG_HOME variables. 
    Note: the $ARTIFACTORY_HOME variable points to your existing installation, and the $JFROG_HOME variable points to the new installation.

    export ARTIFACTORY_HOME=<Path to your current Artifactory installation> 
    export JFROG_HOME=<Full path to jfrog directory>
    export JF_PRODUCT_HOME=$JFROG_HOME/artifactory
  4. Copy the directories from your current to the new path.

    Mandatory Steps

    # Artifactory data
    mkdir -p $JFROG_HOME/artifactory/var/data/artifactory/
    cp -rp $ARTIFACTORY_HOME/data/. $JFROG_HOME/artifactory/var/data/artifactory/
    
    # Access data
    mkdir -p $JFROG_HOME/artifactory/var/data/access/
    cp -rp $ARTIFACTORY_HOME/access/data/. $JFROG_HOME/artifactory/var/data/access/
    
    # Replicator data
    # Note: If you've have never used the Artifactory Replicator 
    # your $ARTIFACTORY_HOME/replicator/ directory will be empty
    mkdir -p $JFROG_HOME/artifactory/var/data/replicator/
    cp -rp $ARTIFACTORY_HOME/replicator/data/. $JFROG_HOME/artifactory/var/data/replicator/
    
    # Artifactory config
    mkdir -p $JFROG_HOME/artifactory/var/etc/artifactory/
    cp -rp $ARTIFACTORY_HOME/etc/. $JFROG_HOME/artifactory/var/etc/artifactory/
    
    # Access config
    mkdir -p $JFROG_HOME/artifactory/var/etc/access/
    cp -rp $ARTIFACTORY_HOME/access/etc/. $JFROG_HOME/artifactory/var/etc/access/
    
    # Replicator config
    # Note: If you have never used the Artifactory Replicator 
    # your $ARTIFACTORY_HOME/replicator/ directory will be empty
    mkdir -p $JFROG_HOME/artifactory/var/etc/replicator/
    cp -rp $ARTIFACTORY_HOME/replicator/etc/. $JFROG_HOME/artifactory/var/etc/replicator/
    
    # master.key
    mkdir -p $JFROG_HOME/artifactory/var/etc/security/
    cp -p $ARTIFACTORY_HOME/etc/security/master.key $JFROG_HOME/artifactory/var/etc/security/master.key
    
    # server.xml
    mkdir -p $JFROG_HOME/artifactory/var/work/
    cp -p $ARTIFACTORY_HOME/tomcat/conf/server.xml $JFROG_HOME/artifactory/var/work/server.xml
    
    # artifactory.defaults
    cp -rp $ARTIFACTORY_HOME/bin/artifactory.default  $JFROG_HOME/artifactory/var/work/artifactory.default
    #or, if Artifactory was installed a service
    cp -rp $ARTIFACTORY_HOME/etc/default $JFROG_HOME/artifactory/var/work/artifactory.default
    
    # External database driver, for example: mysql-connector-java-<version>.jar
    mkdir -p $JFROG_HOME/artifactory/var/bootstrap/artifactory/tomcat/lib
    cp -rp $ARTIFACTORY_HOME/tomcat/lib/<your database driver> $JFROG_HOME/artifactory/var/bootstrap/artifactory/tomcat/lib/<your database driver>
    
    # Remove logback.xml with old links. Please consider migrating manually anything that is customized here
    rm -f $JFROG_HOME/artifactory/var/etc/artifactory/logback.xml
    rm -f $JFROG_HOME/artifactory/var/etc/access/logback.xml
    
    # Move Artifactory logs
    mkdir -p $JFROG_HOME/artifactory/var/log/archived/artifactory/
    cp -rp $ARTIFACTORY_HOME/logs/. $JFROG_HOME/artifactory/var/log/archived/artifactory/

    Optional Steps

    # Artifactory backup (optional)
    mkdir -p $JFROG_HOME/artifactory/var/backup/artifactory/
    cp -rp $ARTIFACTORY_HOME/backup/. $JFROG_HOME/artifactory/var/backup/artifactory/
    
    # Access backup (optional)
    mkdir -p $JFROG_HOME/artifactory/var/backup/access/
    cp -rp $ARTIFACTORY_HOME/access/data/. $JFROG_HOME/artifactory/var/backup/access/
    
    # Replicator backup (optional)
    mkdir -p $JFROG_HOME/artifactory/var/backup/replicator/
    cp -rp $ARTIFACTORY_HOME/replicator/data/. $JFROG_HOME/artifactory/var/backup/replicator/
    
    # Access logs (optional)
    mkdir -p $JFROG_HOME/artifactory/var/log/archived/access/
    cp -rp $ARTIFACTORY_HOME/access/logs/. $JFROG_HOME/artifactory/var/log/archived/access/
    
    # Replicator logs (optional)
    mkdir -p $JFROG_HOME/artifactory/var/log/archived/replicator/
    cp -rp $ARTIFACTORY_HOME/replicator/logs/. $JFROG_HOME/artifactory/var/log/archived/replicator/
  5. For HA installations, replace any relative paths in the $ARTIFACTORY_HOME/etc/ha-node.properties file with absolute paths.

    For example:
    # relative path
    artifactory.ha.data.dir=artifactory-ha
    # absolute path
    artifactory.ha.data.dir=/var/opt/jfrog/artifactory-ha
  6. Run the migration script with the same privileges as you have in your current Artifactory installation. This script will copy over and translate your current configurations to the new configuration format, according to the new file system layout.

    The migration script only migrates configuration values. Any comments added to the configuration files in the Artifactory 6.x installation will not be migrated.

    cd $JFROG_HOME/artifactory/app/bin
    ./migrate.sh
  7. Check that the migration has completed successfully, by reviewing the following files:

    1. migration log$JFROG_HOME/artifactory/var/log/migration.log

    2. system.yaml configuration$JFROG_HOME/artifactory/var/etc/system.yaml
      This newly created file will contain your current custom configurations in the new format.

  8. If Artifactory was installed as a service in previous version, install this version also as a service.

    When an earlier version is installed as a service, it is important to update the new one also as a service. Otherwise a restart of the server may lead to older version of Artifactory coming up.

    cd $JFROG_HOME/artifactory/app/bin
    ./installService.sh
  9. Manage Artifactory.

    $JFROG_HOME/artifactory/app/bin/artifactoryctl start|stop|check
  10. Access Artifactory from your browser at: http://SERVER_HOSTNAME:8082/ui/For example, on your local machine: http://localhost:8082/ui/

    If you had a reverse proxy or load balancer configured with your Artifactory 6.x, you will need to create a new reverse proxy configuration and update your reverse proxy settings.
    You can generate a new configuration template by accessing the upgraded Artifactory server UI (by default http://localhost:8082/ui/), navigate to 
    Administration > Artifactory > General > HTTP Settings adjust your Reverse Proxy Settings and generate a new configuration template. See more information about reverse proxy settings


  11. Check Artifactory Log.

    tail -f $JFROG_HOME/artifactory/var/log/console.log

Docker Compose Upgrade

  1. Stop and remove the current containers.

    Upgrading from docker run
    docker stop artifactory
    docker rm -f artifactory 
    Upgrading from docker compose available at https://bintray.com/jfrog/run/art-compose
    docker stop artifactory postgresql  nginx
    docker rm -f artifactory postgresql  nginx
  2. Extract the contents of the compressed archive and go to the extracted folder.

    tar -xvf jfrog-artifactory-<pro|oss|cpp-ce>-<version>-compose.tar.gz

    .env file included within the Docker-Compose archive

    This .env file is used by docker-compose and is updated during installations and upgrades.

    Notice that some operating systems do not display dot files by default. If you make any changes to the file, remember to backup before an upgrade.

  3. Run the config.sh script to setup folders with required ownership.

    ./config.sh
  4. Check that the migration has completed successfully, by reviewing the following files:

    1. migration log$JFROG_HOME/artifactory/var/log/migration.log

    2. system.yaml configuration$JFROG_HOME/artifactory/var/etc/system.yamlThis newly created file will contain your current custom configurations in the new format.

    3. Depending on your choices, a selected docker-compose.yaml will be available in the extracted folder. However, there are a few docker-compose templates in the directory templates.You can choose any template and copy it to the extracted folder as docker-compose.yaml

  5. Manage Artifactory using native Docker Compose commands: docker-compose -p rt <action> command.

    docker-compose -p rt ps
    docker-compose -p rt up -d
    docker-compose -p rt down
  6. Access Artifactory from your browser at: http://SERVER_HOSTNAME:8082/ui/For example, on your local machine: http://localhost:8082/ui/

    If you had a reverse proxy or load balancer configured with your Artifactory 6.x, you will need to create a new reverse proxy configuration and update your reverse proxy settings.
    You can generate a new configuration template by accessing the upgraded Artifactory server UI (by default http://localhost:8082/ui/), navigate to 
    Administration > Artifactory > General > HTTP Settings adjust your Reverse Proxy Settings and generate a new configuration template. See more information about reverse proxy settings.

  7. Check Artifactory Log.

    tail -f $JFROG_HOME/artifactory/var/log/console.log

RPM Upgrade

  1. Stop the current server.

    service artifactory stop
  2. Install Artifactory as a service on Red Hat compatible Linux distributions, as a root user.

    yum -y install jfrog-artifactory-<pro|oss|cpp-ce>-<version>.rpm
  3. Check that the migration has completed successfully, by reviewing the following files:

    1. migration log$JFROG_HOME/artifactory/var/log/migration.log

    2. system.yaml configuration$JFROG_HOME/artifactory/var/etc/system.yaml
      This newly created file will contain your current custom configurations in the new format.

  4. Manage Artifactory.

    service artifactory start|stop
  5. Access Artifactory from your browser at: http://SERVER_HOSTNAME:8082/ui/For example, on your local machine: http://localhost:8082/ui/

    If you had a reverse proxy or load balancer configured with your Artifactory 6.x, you will need to create a new reverse proxy configuration and update your reverse proxy settings.
    You can generate a new configuration template by accessing the upgraded Artifactory server UI (by default http://localhost:8082/ui/), navigate to 
    Administration > Artifactory > General > HTTP Settings adjust your Reverse Proxy Settings and generate a new configuration template. See more information about reverse proxy settings.

  6. Check Artifactory Log.

    tail -f $JFROG_HOME/artifactory/var/log/console.log

Debian Upgrade

  1. Stop the current server.

    service artifactory stop
  2. Install Artifactory as a service on a Debian compatible Linux distributions, as a root user.

    Run Installation
    dpkg -i jfrog-artifactory-<pro|oss|cpp-ce>-<version>.deb
  3. Check that the migration has completed successfully, by reviewing the following files:

    1. migration log$JFROG_HOME/artifactory/var/log/migration.log

    2. system.yaml configuration$JFROG_HOME/artifactory/var/etc/system.yaml
      This newly created file will contain your current custom configurations in the new format.

  4. Manage Artifactory.

    service artifactory start|stop
  5. Access Artifactory from your browser at: http://SERVER_HOSTNAME:8082/ui/For example, on your local machine: http://localhost:8082/ui/

    If you had a reverse proxy or load balancer configured with your Artifactory 6.x, you will need to create a new reverse proxy configuration and update your reverse proxy settings.
    You can generate a new configuration template by accessing the upgraded Artifactory server UI (by default http://localhost:8082/ui/), navigate to 
    Administration > Artifactory > General > HTTP Settings adjust your Reverse Proxy Settings and generate a new configuration template. See more information about reverse proxy settings.

  6. Check Artifactory Log.

    tail -f $JFROG_HOME/artifactory/var/log/console.log

Windows Upgrade

Migration is a manual process for a Windows installation. The below steps also include copying directories over and running the migration script

Make sure to run all commands on the server with the user that's running Artifactory.

  1. Stop the current server.

    cd %ARTIFACTORY_HOME%\bin
    artifactory.bat stop
  2. Extract the contents of the compressed archive, move it into a newly created jfrog\artifactory folder, and go to the new folder.

    # Uncompress the zip file from windows interface
    mkdir jfrog
    move jfrog-artifactory-<pro|oss|cpp-ce>-<version>-windows\artifactory-<pro|oss|cpp-ce>-<version> jfrog\artifactory
  3. Set your ARTIFACTORY_HOME and JFROG_HOME variables. 
    Note: the $ARTIFACTORY_HOME variable points to your existing installation, and the $JFROG_HOME variable points to the new installation.

    When setting the ARTIFACTORY_HOME and JFROG_HOME variables, make sure to use Windows short name or escape space. For more information, see here.

    SET ARTIFACTORY_HOME=<Path to your current Artifactory installation> 
    SET JFROG_HOME=<Path to jfrog folder>
  4. Copy the directories from your current to the new path. Ignore if the target directory exists.

    Mandatory Steps

    # Artifactory data 
    
    mkdir %JFROG_HOME%\artifactory\var\data\artifactory
    xcopy %ARTIFACTORY_HOME%\data %JFROG_HOME%\artifactory\var\data\artifactory /E /q
     
    # Access data
    mkdir %JFROG_HOME%\artifactory\var\data\access
    xcopy %ARTIFACTORY_HOME%\access\data %JFROG_HOME%\artifactory\var\data\access /E /q
     
    # Replicator data
    # Note: If you've have never used the Artifactory Replicator
    # your %ARTIFACTORY_HOME%\replicator directory will be empty
    mkdir %JFROG_HOME%\artifactory\var\data\replicator
    xcopy %ARTIFACTORY_HOME%\replicator\data %JFROG_HOME%\artifactory\var\data\replicator /E /q
     
    # Artifactory config
    mkdir %JFROG_HOME%\artifactory\var\etc\artifactory
    xcopy %ARTIFACTORY_HOME%\etc %JFROG_HOME%\artifactory\var\etc\artifactory /E /q
     
    # Access config
    mkdir %JFROG_HOME%\artifactory\var\etc\access
    xcopy %ARTIFACTORY_HOME%\access\etc %JFROG_HOME%\artifactory\var\etc\access /E /q
     
    # Replicator config
    # Note: If you've have never used the Artifactory Replicator
    # your %ARTIFACTORY_HOME%\replicator directory will be empty
    mkdir %JFROG_HOME%\artifactory\var\etc\replicator
    xcopy %ARTIFACTORY_HOME%\replicator\etc %JFROG_HOME%\artifactory\var\etc\replicator /E /q
    
    # master.key
    mkdir %JFROG_HOME%\artifactory\var\etc\security
    xcopy %ARTIFACTORY_HOME%\etc\security\master.key %JFROG_HOME%\artifactory\var\etc\security /q
     
    # server.xml
    mkdir %JFROG_HOME%\artifactory\var\work
    xcopy %ARTIFACTORY_HOME%\tomcat\conf\server.xml %JFROG_HOME%\artifactory\var\work /q
     
    # External database driver, for example: mysql-connector-java-<version>.jar
    xcopy %ARTIFACTORY_HOME%\tomcat\lib\<your database driver> %JFROG_HOME%\artifactory\app\artifactory\tomcat\lib /q
    
    # Change ownership of new Artifactory directory to the user intended to run Artifactory.
    # This can be skipped if you performed all previous steps with the user intended to run Artifactory.
    
    # Remove logback.xml with old links. Please consider migrating manually anything that is customized here
    del %JFROG_HOME%\artifactory\var\etc\artifactory\logback.xml
    del %JFROG_HOME%\artifactory\var\etc\access\logback.xml


    Optional Steps

    # Artifactory backup (optional)
    
    mkdir %JFROG_HOME%\artifactory\var\backup\artifactory
    xcopy %ARTIFACTORY_HOME%\backup %JFROG_HOME%\artifactory\var\backup\artifactory /E /q
     
    # Access backup (optional)
    mkdir %JFROG_HOME%\artifactory\var\backup\access
    xcopy %ARTIFACTORY_HOME%\access\backup %JFROG_HOME%\artifactory\var\backup\access /E /q
     
    # Replicator backup (optional)
    mkdir %JFROG_HOME%\artifactory\var\backup\replicator
    xcopy %ARTIFACTORY_HOME%\replicator\backup %JFROG_HOME%\artifactory\var\backup\replicator /E /q
     
    # Artifactory logs (optional)
    mkdir %JFROG_HOME%\artifactory\var\log\artifactory
    xcopy %ARTIFACTORY_HOME%\logs %JFROG_HOME%\artifactory\var\log\artifactory /E /q
     
    # Access logs (optional)
    mkdir %JFROG_HOME%\artifactory\var\log\access
    xcopy %ARTIFACTORY_HOME%\access\logs %JFROG_HOME%\artifactory\var\log\access /E /q
     
    # Replicator logs (optional)
    mkdir %JFROG_HOME%\artifactory\var\log\replicator
    xcopy %ARTIFACTORY_HOME%\replicator\logs %JFROG_HOME%\artifactory\var\log\replicator /E /q
    
    
    # Copy specific files from your current to the new path.
  5. For HA installations, replace any relative paths in the %ARTIFACTORY_HOME%\etc\ha-node.properties file with absolute paths.

    For example:
    # relative path
    artifactory.ha.data.dir=artifactory-ha
    # absolute path
    artifactory.ha.data.dir=\var\opt\jfrog\artifactory-ha
  6. Run the migration script with the same privileges as you have in your current Artifactory installation. This script will copy over and translate your current configurations to the new configuration format, according to the new file system layout.

    cd %JFROG_HOME%\artifactory\app\bin
    migrate.bat

    The migration script only migrates configuration values. Any comments added to the configuration files in the Artifactory 6.x installation will not be migrated.

  7. Check that the migration has completed successfully, by reviewing the following files:
    1. migration log: %JFROG_HOME%\artifactory\var\log\migration.log

    2. system.yaml configuration: %JFROG_HOME%\artifactory\var\etc\system.yaml
      This newly created file will contain your current custom configurations in the new format.

    3. Manage Artifactory.

      %JFROG_HOME%\artifactory\app\bin\artifactory.bat start|stop

      Firewall Alerts for first time Artifactory Windows Installation

      When starting Artifactory, you may get some firewall exception messages. Please select private networks and allow access to continue working.
  8. Access Artifactory from your browser at: http://SERVER_HOSTNAME:8082/ui/For example, on your local machine: http://localhost:8082/ui/

    If you had a reverse proxy or load balancer configured with your Artifactory 6.x, you will need to create a new reverse proxy configuration and update your reverse proxy settings.
    You can generate a new configuration template by accessing the upgraded Artifactory server UI (by default http://localhost:8082/ui/), navigate to 
    Administration > Artifactory > General > HTTP Settings adjust your Reverse Proxy Settings and generate a new configuration template. See more information about reverse proxy settings.


  9. Check Artifactory Log.

    type %JFROG_HOME%\artifactory\var\log\console.log

Upgrading from Version 7.x to 7.x

The following upgrade methods are supported:

Linux Archive Upgrade

  1. Stop the current server.

    Stop Artifactory
    cd $JFROG_HOME/artifactory/app/bin
    ./artifactoryctl stop
  2. Extract the contents of the compressed archive and go to the extracted folder.

    Untar
    tar -xvf jfrog-artifactory-<pro|oss|cpp-ce>-<version>-linux.tar.gz
  3. Replace the existing $JFROG_HOME/artifactory/app with the new app folder.

    Upgrade
    # Export variables to simplify commands
    export JFROG_HOME=<Your JFrog home directory, for example /opt/jfrog>
    export JF_NEW_VERSION=<For example /opt/jfrog/artifactory-7.x>
    
    # Remove app
    rm -rf $JFROG_HOME/artifactory/app
    
    # Copy new app
    cp -r $JF_NEW_VERSION/app $JFROG_HOME/artifactory
    
    # Remove extracted new version
    rm -rf $JF_NEW_VERSION
    
  4. Manage Artifactory.

    $JFROG_HOME/artifactory/app/bin/artifactoryctl start|stop|check
  5. Access Artifactory from your browser at: http://SERVER_HOSTNAME:8082/ui/. For example, on your local machine: http://localhost:8082/ui/.

  6. Check Artifactory Log.

    tail -f $JFROG_HOME/artifactory/var/log/console.log

RPM Upgrade

  1. Stop the current server.

    service artifactory stop
  2. Install Artifactory as a service on Red Hat compatible Linux distributions, as a root user.

    yum -y install jfrog-artifactory-<pro|oss|cpp-ce>-<version>.rpm
  3. Manage Artifactory.

    service artifactory start|stop
  4. Access Artifactory from your browser at: http://SERVER_HOSTNAME:8082/ui/For example, on your local machine: http://localhost:8082/ui/

  5. Check Artifactory Log.

    tail -f $JFROG_HOME/artifactory/var/log/console.log

Docker Compose Upgrade

  1. Stop the current server.

    docker-compose -p rt stop
  2.  Extract the contents of the compressed archive and go to the extracted folder.

    tar -xvf jfrog-artifactory-<pro|oss|cpp-ce>-<version>-compose.tar.gz

    If you've made changes to the .env file in a previous installation, reconcile the changes to the file within this archive. When run, the script will also read configuration from the system.yaml and update this file.

  3. Run the config.sh script to setup folders with required ownership.

    bin/config.sh
  4. Manage Artifactory using native Docker Compose commands, docker-compose -p rt <action> command.

    docker-compose -p rt ps
    docker-compose -p rt up -d
    docker-compose -p rt down
  5. Access Artifactory from your browser at: http://SERVER_HOSTNAME:8082/ui/For example, on your local machine: http://localhost:8082/ui/

  6. Check Artifactory Log.

    tail -f $ROOT_DATA_DIR/var/log/console.log

Debian Upgrade

  1. Stop the current server.

    service artifactory stop
  2. Install Artifactory as a service on compatible Linux distributions, as a root user.

    Run Installation
    dpkg -i jfrog-artifactory-<pro|oss|cpp-ce>-<version>.deb
  3. Manage Artifactory.

    service artifactory start|stop
  4. Access Artifactory from your browser at: http://SERVER_HOSTNAME:8082/ui/For example, on your local machine: http://localhost:8082/ui/

  5. Check Artifactory Log.

    tail -f $JFROG_HOME/artifactory/var/log/console.log

Windows Upgrade

  1. Stop the current server.

    Stop Artifactory
    cd %JFROG_HOME%\artifactory\app\bin
    artifactory.bat stop
  2. Extract the contents of the compressed archive and go to the extracted folder.


  3. Replace the existing %JFROG_HOME%\app with the new app folder.

    Upgrade
    # Export variables to simplify commands, Example paths provided here
    SET %JFROG_HOME%=\myHome\jfrog
    SET %JF_NEW_VERSION%=\myHome\artifactory-7.x
    
    # Remove app
    rmdir %JFROG_HOME%app\jfrog\artifactory
    
    # Copy new app
    copy %$JF_NEW_VERSION%\app %$JFROG_HOME%\artifactory
    
    # Remove extracted new version
    rmdir %JF_NEW_VERSION%
    
  4. Manage Artifactory.

    %JFROG_HOME%\artifactory\app\bin\artifactory.bat start|stop

    Firewall Alerts for first time Artifactory Windows Installation

    When starting Artifactory, you may get some firewall exception messages. Please select private networks and allow access to continue working.

  5. Access Artifactory from your browser at: http://SERVER_HOSTNAME:8082/ui/. For example, on your local machine: http://localhost:8082/ui/.

  6. Check Artifactory Log.

    type %JFROG_HOME%\artifactory\var\log\console.log

Upgrading an Enterprise HA Cluster

This section describes the process to upgrade your Artifactory Enterprise High Availability cluster. Since your cluster contains more than one node, you may complete the upgrade process without incurring any down time to the Artifactory service your organization is using.

Upgrade Steps

Upgrading to the latest version includes the following three phases:

  1. Upgrading the first node.
  2. Upgrading the additional nodes.
  3. Verifying the HA installation and configuration.

Want to stop using NFS?

To stop using a shared NFS once the upgrade procedure is complete (optional), refer to Migrating Data from NFS to migrate to alternative storage.

Using the UI without sticky sessions during an upgrade

If you do not configure your HA cluster to enable sticky sessions, the UI will not work until you have completed upgrading the whole cluster. To learn about configuring sticky sessions for an HA cluster, please refer to Session Management.

Upgrading the First Node

  1. Remove the first node from the load balancer. All requests will be directed to the additional nodes. Check the $HOME/logs/request.log and ARTIFACTORY_URL/api/tasks (search for "running") to ensure that Artifactory is completely inactive.
  2. Perform a graceful shutdown of the first node. While the first node is down, the load balancer should redirect all queries to the additional nodes.
  3. Continue with the upgrade according to the instructions for your installation type.

  4. Start up the first node. It will recognize that the HA cluster nodes are not all running the same version of Artifactory, and consequently, the system will be limited to allowing uploads and downloads. 

    Any attempt to perform other actions such as changing the DB schema, modifying permissions, changing repository configuration and more, are strictly blocked. This limitation will continue until all the cluster nodes are once again running the same version.

    Version inconsistency generates exceptions

    Running the HA cluster nodes with different versions generates exceptions. These can be seen in the log files and reflect the temporary inconsistent state during the upgrade process. This is normal and should be ignored until all the cluster nodes are, once again, running the same version.

  5. When upgrading from Version 6.x and to 7.x
    Adjust your reverse proxy settings and update your load balancer configuration to use the new JFrog Platform URL http://<hostname>:8081.
  6. Put the first node back to the load balancer.

Upgrading the additional Node

For each additional node in your HA cluster, perform the following steps:

  1. Remove the node from the load balancer, so all requests are directed to the other nodes. Check the $HOME/logs/request.log and ARTIFACTORY_URL/api/tasks (search for "running") to ensure that Artifactory is completely inactive.
  2. Perform a graceful shutdown of the node. While the node is down, the load balancer should redirect all queries to the other nodes.

  3. Continue with the upgrade according to the instructions for your installation type.

  4. Start up the additional node.
  5. Add the secondary node back to the load balancer.
  6. Repeat this process for each secondary node.

Check your installation

After starting up each secondary node, we recommend inspecting the system.yaml and binarystore.xml files (under $JFROG_HOME/artifactory/var/etc/) to ensure they are correctly configured 

Verify the HA Installation and Configuration

Once you have completed upgrading your HA cluster, you can verify that your cluster has been installed and configured correctly using the following tests.

  1. Directly Access the Artifactory UI for the server you have just configured
  2. In the Admin module go to Service | Artifactory | System Logs to view the log and verify that you see an entry for HA Node ID.
  3. The bottom of the module navigation bar should also indicate that you are running with an Enterprise license. In case of an error you will see an error message in the page header.
  4. Access Artifactory through your load balancer and log in as Admin.
  5. In the Admin module go to Monitoring | Service Status. When selected the following table including details on all the Artifactory nodes in your cluster will be displayed.

  6. In the Admin module under General | Settings, verify that the Custom URL Base field is correctly configured to the URL of the Load Balancer.


Copyright © 2020 JFrog Ltd.