The database (a file called persistence.mv.db) is created when the node first starts up. By default, it has an
administrator user sa and a blank password. The node requires the user with administrator permissions in order to
creates tables upon the first startup or after deploying new CorDapps with their own tables. The database password is
required only when the H2 database is exposed on non-localhost address (which is disabled by default).

Note that changing the user/password for the existing node in node.conf will not update them in the H2 database.
You need to log into the database first to create a new user or change a user’s password.

Nodes backed by an H2 database will not expose this database by default. To configure the node to expose its internal
database over a socket which can be browsed using any tool that can use JDBC drivers, you must specify the full network
address (interface and port) using the h2Settings syntax in the node configuration.

The configuration below will restrict the H2 service to run on localhost:

h2Settings{address:"localhost:12345"}

If you want H2 to auto-select a port (mimicking the old h2Port behaviour), you can use:

h2Settings{address:"localhost:0"}

If remote access is required, the address can be changed to 0.0.0.0 to listen on all interfaces. A password must be
set for the database user before doing so.

You can also use the H2 Console to connect directly to the node’s persistence.mv.db file. Ensure the node is off
before doing so, as access to the database file requires exclusive access. If the node is still running, the H2 Console
will return the following error:
Databasemaybealreadyinuse:null.Possiblesolutions:closeallotherconnection(s);usetheservermode[90020-196].