Repository Management with Nexus
7.2. Enabling Smart Proxy Publishing
In order to enable the Smart Proxy feature on your Nexus instance, you need to navigate to the global Smart Proxy configuration screen. It is available in the left hand navigation in the Enterprise section. Selecting Smart Proxy will show you the configuration screen displayed in Figure 7.1, “Global Configuration for Smart Proxy”.
The Network Settings section allows you to enable the Smart Proxy server with a check-box. This will need to be enabled on all servers that will publish events in the Smart Proxy network, while servers that will only act as subscribers can leave this option disabled.
In addition you can configure the address and port at which the publishing server will be available. The default address of 0.0.0.0 will cause the proxy to listen on all addresses. The default port number of 0 will trigger usage of a random available port number for connection listening. If a random port is used, it will be chosen when the server (re)starts.
With the Advertised URI field it is possible to configure a specific address to be broad-casted by the proxy to the subscribing Smart Proxy clients enabling e.g. usage of a publicly available fully qualified host-name including the domain or also just usage of an externally reachable IP number.
It is important to enable the configured connection ports on any firewall between the servers to allow the direct socket connection between the servers and to avoid using random ports.
The Status field below the form will show the current status of the Smart Proxy including the full address and port.
The Public Key field displays the key identifying this server instance. It is automatically populated with the certificate associated with the public/private key pair that is generated when the server is first run.
The key is stored in sonatype-work/nexus/conf/keystore/private.ks and identifies this server. If you copy the sonatype work folder from one server to another as part of a migration or a move from testing to staging or production you will need to ensure that keys are not identical between multiple servers. To get a new key generated simply remove the key-store file and restart Nexus.