.
Refer to the book for detailed descriptions of the Nexus runtime directory and file structures.
There are important directories to be aware of when managing a Nexus Repository Manager installation.
In the screenshot, we can see examples of how it might look when different versions of the repository manager are unpacked over time.
Installation Directory (1)
This is the common parent directory in which all files related to the Sonatype Nexus Repository Manager will reside. This directory is created by you manually at a location of your choice. Its purpose is to eventually contain the Application Directory and Data Directory and be the common operating system location for all files related to Nexus Repository Manager.
Application Directory (2, 3, 4)
A subdirectory of the Installation Directory, it contains the per version runtime application binary files used to launch and run Nexus. This includes Eclipse Jetty Server components, Nexus core libraries and control scripts. The name of this directory follows a pattern depending on the distribution used:
2 Nexus 2.x OSS Edition: nexus-<version>
4 Nexus 2.x Professional Edition: nexus-professional-<version>
3 Nexus 3.x OSS or Pro Edition: nexus-<version>
The Application Directory is created when a bundle distribution is extracted.
Work Directory (5) or Data Directory (6)
This is the main directory that stores your runtime specific Nexus configuration and component/artifact related files. The default location depends on what installer archive was extracted.
5 Nexus 2.x: under the Installation Directory as sonatype-work/nexus6 Nexus 3.x: under the Installation Directory as sonatype-work/nexus3
If missing, the Data Directory or Work Directory are created when a bundle distribution is extracted. Any required runtime contents are created automatically on first Nexus startup.