System Requirements
Before you install Artifactory please refer toSystem Requirementsfor information on supported platforms, supported browsers and other requirements.
Installation
Changing the Default Database
A default installation of Artifactory works with a Derby Database, however for better performance and to reuse existing infrastructures you can configure Artifactory to work with alternative storage solutions.
For details please refer toChanging the Default Storage.
Directory Structure
After installing Artifactory, the$ARTIFACTORY_HOMEdirectory will contain the following directory structure (the$ARTIFACTORY_HOMEdirectory location depends on your installation type):
File/Folder |
Description |
|---|---|
|
Artifactory log files (general, access, request etc.) |
etc |
Configuration files |
etc/plugins |
Custom Groovy user plugins. |
etc/security |
Global security related files (configuring global encryption key, PGP signing key etc.). |
etc/ui |
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. |
bin |
Artifactory startup/shutdown scripts. |
|
The default tomcat directory bundled with Artifactory. |
tomcat/work |
tmp目录tomcat和JVM使用(tomcatautomaticallyassigns it to a java system environment variable asjava.io.tmpdir) |
tomcat/logs |
Additional Tomcat log files |
misc |
Configuration files used as examples for different databases and servlet containers. |
|
The default backup directory Artifactory uses for system wide and repository backup. |
webapps |
Contains the Artifactory WAR file used by the bundled tomcat distribution. |
HTTP Server
You can run Artifactory with one of the supported HTTP servers set up as a front end. For details please refer toRunning Behind an HTTP Server.