Need help with other JFrog products?
This section provides a guide on the different ways you can install and configure Artifactory.
Installing Artifactory HA
There are different instructions for installing Artifactory HA
If you are installing an Artifactory HA cluster, please refer to HA Installation and Setup.
If you follow the instructions on this page for an installation of Artifactory HA, your HA cluster will not work.
Before you install Artifactory please refer to System Requirements for information on supported platforms, supported browsers and other requirements.
The installation procedure involves the following main steps:
- Installing Artifactory
- Configuring the database
- Configuring the filestore
- Configuring an HTTP Server (Optional)
For detailed instructions, visit one of the following platform-specific pages:
Configuring the Database
Artifactory comes with an embedded Derby Database out-of-the-box which it is pre-configured to use, however, for better performance and to reuse existing infrastructures you may have, you can configure Artifactory to work with alternative supported databases.
For details please refer to Configuring the Database.
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. For details, please refer to Configuring the Filestore.
Configuring an HTTP Server
You can run Artifactory with one of the supported HTTP servers set up as a front end. For details please refer to Configuring a Reverse Proxy.
After installing Artifactory, the
$ARTIFACTORY_HOME directory will contain the following directory structure (the
$ARTIFACTORY_HOME directory location depends on your installation type):
|access||The home directory of the bundled JFrog Access. More details in the Access Tokens page.|
|access/etc/keys||JFrog Access keys. More details in the Access Tokens page.|
|Artifactory log files (general, access, request etc.)|
|Custom Groovy user plugins.|
|Global security related files (configuring global encryption key, PGP signing key etc.).|
|Manually uploaded custom UI logos.|
|The Derby database (only present when using Derby).|
|The checksum based storage of binaries when using the default filesystem storage.|
|Directory to save temporary files which Artifactory generates.|
|Directory to save files uploaded using the Web UI.|
|Artifactory startup/shutdown scripts.|
|The default tomcat directory bundled with Artifactory.|
|The tmp directory tomcat and the JVM uses (Tomcat automatically assigns it to a java system environment variable as |
|Additional Tomcat log files|
|Configuration files used as examples for different databases and servlet containers.|
|The default backup directory Artifactory uses for system wide and repository backup.|
|Contains the Artifactory WAR file and the Access WAR file used by the bundled Tomcat distribution. We strongly recommend keeping both these files in the same bundled Tomcat.|
Default Admin User
Once installation is complete, Artifactory has a default user with admin privileges predefined in the system:
Change the admin password
We strongly recommend changing the admin password as soon as installation is complete.
Watch the Screencast
Please refer to the main Troubleshooting page.