Page tree
Skip to end of metadata
Go to start of metadata

System Requirements

Before you install Artifactory please refer to System Requirements for information on supported platforms, supported browsers and other requirements.

Installation

Page Contents

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.

Directory Structure

After installing Artifactory, the $ARTIFACTORY_HOME directory will contain the following directory structure (the $ARTIFACTORY_HOME directory location depends on your installation type):

File/Folder

Description

logs

Artifactory log files (general, access, request etc.)
etcConfiguration files
etc/pluginsCustom Groovy user plugins.
etc/securityGlobal security related files (configuring global encryption key, PGP signing key etc.).
etc/uiManually uploaded custom UI logos.

data/derby

The Derby database (only present when using Derby).

data/filestore

The checksum based storage of binaries when using the default filesystem storage.

data/tmp/work

Directory to save temporary files which Artifactory generates.

data/tmp/artifactory-uploads

Directory to save files uploaded using the Web UI.
binArtifactory startup/shutdown scripts.

tomcat

The default tomcat directory bundled with Artifactory.
tomcat/workThe tmp directory tomcat and the JVM uses (Tomcat automatically assigns it to a java system environment variable as java.io.tmpdir)
tomcat/logsAdditional Tomcat log files
miscConfiguration files used as examples for different databases and servlet containers.

backup

The default backup directory Artifactory uses for system wide and repository backup. 
webappsContains 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 to Running Behind an HTTP Server.

  • No labels