Add licenses according to your license type.
Option 1: Copy the
artifactory.cluster.licensefile to the first node's configuration directory.
cp artifactory.cluster.license $JFROG_HOME/artifactory/var/etc/artifactory/
This can also be done once you start Artifactory using:
Specifying multiple licenses
Whether in the Artifactory UI, using the REST API or in the
artifactory.cluster.license file, make sure that the licenses are separated by a newline.
Applying a license bucket requires JFrog Mission Control.
Complete configuring and starting the first node.
Enable Mission Control microservice in Artifactory.
After installing and before running Artifactory, you may set the following configurations.
System YAML Configuration File
Where to find system.yaml?
If you don't have a System YAML file in your folder, copy the template available in the folder and name it
For the Helm charts, the
system.yamlfile is managed in the chart’s
Artifactory comes with an embedded Derby Database out-of-the-box. If you're planning to use it in production, it is highly recommended to first Configure the Database, and then start Artifactory.
Customize Java Opts (optional)Remember to modify your JVM Parameters as needed by setting
JAVA_OPTIONSin Shared Configurations. The property to pass extra Java opts is
artifactory.extraJavaOpts. It is highly recommended to set your Java memory parameters as follows:
The larger your repository or number of concurrent users, the larger you need to make the -Xms and -Xmx values accordingly. If you can reserve at least 512MB for Artifactory, the recommended minimal values are:
-server -Xms512m -Xmx2g -Xss256k -XX:+UseG1GC
For more recommendations about your hardware configuration (especially the -Xmx parameter), see System Requirements
These include: customizing ports, joinKey (join.key), masterKey (master.key).
Configuring the Filestore
By default, Artifactory is configured to use the local file system as its filestore. Artifactory supports a variety of additional filestore configurations to meet a variety of needs for binary storage providers, storage size and redundancy.
Enable TLS 1.0 and 1.1 for Connectivity with Older Databases
Artifactory version 7.25.2 onwards includes OpenJDK version 11.0.11 and later. TLS 1.0 and TLS 1.1 are disabled by default from OpenJDK 11.0.11 onwards. If your database version does not support TLS 1.2, the Artifactory startup fails.
If you are unable to upgrade your database to a version that supports TLS 1.2 or later, perform the following steps to run Artifactory.
Download the java.security file that has TLS 1.0 and 1.1 enabled.
Create the directory,
Copy the java.security file into
Provide the appropriate permissions to the directory.
Artifactory startup takes a backup of the existing java.security file and bootstraps custom java.security into the