Configuring the specifics of the repository manager runtime involves configuration for all components in various configuration files and startup scripts.
This section details these and provides recipes for specific tasks. The main location for configuration files is the etc directory. It includes one properties file and a number of nested directories:.
See Logging and Log Viewer for more information on repository manager logging and the recommended approach for adjusting the logging configuration to meet your needs. This file should not be modified. The bulk of the configuration is contained in this file. This file maintains a list of repositories and all server-wide configuration like the SMTP settings, security realms, repository groups, targets, path mappings and others. Contains configuration for the procurement plugin in Nexus Repository Manager Pro.
After installing the repository manager and creating the nexus symlink as described earlier, your nexus folder contains a conf directory, different than the one discussed above in sonatype-work. The nexus conf directory contains configuration for the Jetty servlet container.
You will only need to modify the files in this directory if you are customizing the configuration of Jetty servlet container or the behavior of the scripts that start the repository manager. This file contains configuration variables which control the behavior of the repository manager and the Jetty servlet container.
If you are customizing the port and host that the repository manager listens to, you change the application-port and application-host properties defined in this file. If you want to customize the location of the sonatype-work directory, you modify the value of the nexus-work property in this configuration file. Changing nexus-webapp-context-path allows you to configure the server context path where repository manager lives.
Configuration files for the Eclipse Jetty servlet container running the repository manager. Jetty users are used to providing a list of jetty XML config files which are merged to form the final configuration. As an advanced configuration option, the repository manager supports this merging concept in its launcher code as of version 2. You can specify additional jetty XML configuration files to load to form the final configuration. The Java Service Wrapper documentation contains more information about this property.
This setup allows for a simple method to add configuration for https, JMX and others by adjusting a few properties. These files cannot be used in version 2. Improve this answer. Brian Matthews Brian Matthews 8, 6 6 gold badges 42 42 silver badges 67 67 bronze badges. Sadly this didn't work to move it to my D: drive with Tomcat7 and Nexus 2.
I tried undeploying and redeploying the webapp. I even tried installing Tomcat on my D: drive. Glenn Lawrence Glenn Lawrence 2, 1 1 gold badge 30 30 silver badges 36 36 bronze badges. VMAtm 27k 17 17 gold badges 76 76 silver badges bronze badges. Fab Marchon Fab Marchon 11 1 1 bronze badge. Manfred Moser Manfred Moser Sign up or log in Sign up using Google. Sign up using Facebook. This directory contains cached reports from the Repository Health Check feature.
This contains the automatically generated key used to identify your repository manager. 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. The main repository manager application log, rotated and compressed daily. Inbound HTTP request log, rotated and compressed daily. 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.
0コメント