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

Artifactory comes with a built-in embedded Derby database that can be reliably used to store data (metadata) for production-level repositories up to hundreds of gigabytes in size.

Accessing a Remote Database

When using an external database, you need a reliable, stable and low-latency network connection to ensure proper functioning of your system.

When using a fullDB configuration, we strongly recommend a high-bandwidth to accommodate the transfer of large BLOBs over the network.

Setup Flow

To setup your new database you need to perform the following steps:

To migrate your existing database:

  • Import the metadata using Full System Import (optional for migration, not required for a new installation). Changing the database does not automatically transfer your data to the new database.

* For a complete step-by-step guide, follow the details in the specific page for each of the supported databases listed below.

Database Connection Settings

Add or change the below parameters for database connections settings under the system.yaml configuration file.

maxOpenConnections
The maximum number of pooled database connections (default: 100).
maxIdleConnections
The maximum number of pooled idle database connections (default: 10).

Default Home Directory

The default product 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 product home directory.



Choosing the Right Database

Artifactory supports the following pluggable database implementations allowing you to change the default to use other popular databases:

For each of the supported databases you can find the corresponding example values in the system.yaml configuration file.

As the default database, Derby provides good performance since it runs in the same process as Artifactory, however, under intensive usage or high load, performance may be degraded since Artifactory and the database compete for shared JVM resources such as caches and memory. Therefore, for Artifactory servers that need to support heavy load, you may consider using an external database such as MySQL or PostgreSQL which are very common choices in many Artifactory installations.

Any of the other supported databases is also a fair choice and may be the practical choice to make if your organization is already using one of them.


Checksum-Based Storage

Artifactory uniquely stores artifacts using checksum-based storage. For details, please refer to Checksum-Based Storage.


Modes of Operation

Artifactory supports two modes of operation:

  • Metadata in the database and binaries stored on the file system (This is the default and recommended configuration).
  • Metadata and binaries stored as BLOBs in the database


Copyright © 2020 JFrog Ltd.