Configuring Nexus Repository Pro for H2 or PostgreSQL

Only available in Nexus Repository Pro. Interested in a free trial?   Start here .

If you're standing up a new instance of Nexus Repository Pro and wish to begin in a new database mode, follow these instructions:

Installing Nexus Repository Pro

  1. Download   the latest Nexus Repository 3 version
  2. Expand and install the archive as with the standard  installation instructions
  3. Follow the instructions for your chosen database

Configuring for the Embedded H2

Create the    <data-dir>/etc/  file and add the following line: 


You can now start your Nexus Repository instance and use an embedded H2 database.

Configuring for External PostgreSQL

To use an external PostgreSQL database, follow these additional instructions:

  1. Create a database in a PostgreSQL server.
  2. Create the   <data-dir>/etc/  file. Add a property to enable external database access:

  3. Note that, by default, the repository manager will detect other nodes accessing the same database. If you wish to modify any of the default values in the <data-dir>/etc/ file pertaining to this setting, you can adjust the following properties:
    • nexus.heartbeat.enabled=true  - This enables the repository manager to detect other nodes accessing the same database. 
    • nexus.heartbeat.interval=600  - This is the time interval for detecting other nodes accessing the same database. By default, this is set to 600 seconds (10 minutes).
    • nexus.heartbeat.history=30  - This configures the number of days to retain old records. By default, this is set to 30 days.
  4. Create a <data-dir>/etc/fabric directory.
  5. In the <data-dir>/etc/fabric directory, create a text file named

    1. Below is a sample that you will need to update with the appropriate configuration. 

      If using AWS Aurora as your database, you will need to include gssEncMode=disable as a query parameter of the JDBC URL.
    2. Note that you can also use the following JVM arguments to specify connection information; you can also specify these in the sonatype-work/nexus3/etc/ file without the preceding -D:

      • -Dnexus.datastore.enabled



    3. You can also pass the following connectivity details as environment variables:

    4. Nexus Repository uses system and environment variables to populate the file; so, configuration via these methods can only be done once. Priority order is as follows:

      • sonatype-work/nexus3/etc/fabric/
      • System properties
      • Environment variables

You can now start your Nexus Repository instance and and use a PostgreSQL database.

Extra Configuration Options for PostgreSQL

Servers under heavy load may also need to configure the connection pool size for the database. Nexus Repository uses a default pool of 100, but you may increase this by appending a line like the following example to :


If you use a container orchestration tool, relational database service, or other infrastructure to launch Nexus Repository, you should configure your maxLifetime for database connections.

Ensure your maxLifetime is set to be several seconds shorter than your infrastructure-imposed connection time limit.

By default, maxLifetime is set to 30 minutes (1800000ms), but you may change this by appending a line like the following example to your file:


How Does Nexus Repository Pro Determine Which Database To Use

If you've omitted nexus.datastore.enabled or set it to false, then Nexus Repository will use OrientDB.

If you've configured nexus.datastore.enabled=true ,  then  Nexus Repository determines which database it is meant to use based on configuration source.

Nexus Repository Pro will look for configuration information from <data-dir>/etc/fabric/ before falling back to the embedded database, which is H2.