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 to Changing the Default Storage.
After installing Artifactory, the
$ARTIFACTORY_HOME directory will contain the following directory structure (the
$ARTIFACTORY_HOME directory location depends on your installation type):
|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 used by the bundled tomcat distribution.|
You can run Artifactory with one of the supported HTTP servers set up as a front end. For details please refer to Running Behind an HTTP Server.