Directories
After you extract the repository manager archive, two directories will appear:
Installation directory
This directory contains the Nexus Repository Manager application and all the required additional components such as Java libraries and configuration files. The name of the directory by default uses nexus- and is appended with the version name. In this section, and throughout the documentation, it is referred to as $install-dir in any code segments.
Data directory
This directory contains all the repositories, components and other data that are stored and managed by the repository manager. The default location of the data directory is ../sonatype-work/nexus3 relative to the installation directory. In this section, and throughout the documentation, it is referred to as $data-dir in any code segments.
Installation Directory
LICENSE.txt , NOTICE.txt
These are files that contain legal details about the license and copyright notices
bin/
This directory contains the nexusstartup script itself as well as startup-related configuration files
etc/
This directory contains configuration files
lib/
This directory contains binary libraries related to Apache Karaf
public/
This directory contains public resources of the application
system/
This directory contains all components and plugins that constitute the application
Data Directory
The data directory contents are unique to each instance and include subdirectories that contain all the components, repositories, configurations and other persistent data used by the repository manager.
The data directory is found by default at ../sonatype-work/nexus3.
To change from the default location see the Configuring the Data Directory section of the Configuring the Runtime Environmentpage.
Files and directories under the data directory include:
blobs/
The parent directory of all file system based blob stores that are not defined with an absolute storage path. For example, the default blob store will live at ../sonatype-work/nexus3/blobs/default .
cache/
This directory contains information on currently cached Karaf bundles
db/
This directory contains the OrientDB databases which are the primary storage for your repository manager’s metadata
elasticsearch/
This directory contains the currently configured state of Elasticsearch
etc/
This directory contains the main runtime configuration and customization of the repository manager. The files are explained further in Configuring the Runtime Environment.
health-check/
This directory contains cached reports from the Repository Health Check feature
keystores/
This contains the automatically generated key used to identify your repository manager
log/
This directory and sub-directories contain active and archived application log files.
You can choose to delete old log files from the logs directory to reclaim disk. Only 90 days of rotated logs are automatically kept.
nexus.log
The main repository manager application log, rotated and compressed daily. Log messages contain standard log output fields including date/time, log level, the associated thread, class and message.
request.log
Inbound HTTP request log, rotated and compressed daily. Log messages include information such as date/time, client IP, authenticated user id, user-agent header value, response status code, bytes sents, and total response time.
outbound-request.log
Outbound request log, rotates daily, maintains 90 days of log files by default, and compresses old logs. The log includes information such as date/time, authenticated user id, method, url, response status code, bytes sent, bytes received, and response time.
jvm.log
Contains JVM stdout, stderr and full thread dumps when explicitly triggered. This log file is normally only relevant when thread dumps need to be extracted from it. This file is not rotated because it should not grow very large. On each application start, the entire contents of this file will be replaced.
karaf.log
This is the Apache Karaf container log file which contains messages specific to the repository manager startup
log/audit/
When Auditing is enabled, audit logs are written to this directory.
audit.log
The active log file is named audit.log. Audit logs are rotated and compressed daily.
log/tasks/
Tasks can generate logs for each execution so that one can better examine what that task did. These log files include messages that would typically be too noisy to put into the main application log. Logs are named by task internal name and a timestamp.
tmp/
This directory is used for temporary storage
Note
Unless you specify a relative path, running Export configuration & metadata for the backup task creates a folder with a snapshot of the databases, in the data directory. See Prepare a Backup for the repository manager to learn how to configure this task.