CENM Database Configuration

Both the Network Map and Identity Manager Components require a persistent layer to be available. This is described in their respective configs with the following configuration state.

  • database:

  • runMigration: Create or upgrade the database schema (database objects like tables, indices) to the current version of the service. If it is set to false, and the database schema is up to date, the service will validate.

  • initialiseSchema: (Deprecated) Automatically creates the tables required by the CENM component.

  • jdbcDriver: Path to the .jar file containing the specific JDBC driver

  • driverClassName: See the specific JDBC driver documentation

  • url: Location of the Database on the network

  • user: Database user

  • password: Database user password

  • additionalProperties: (Optional) Additional database properties

  • lockResolutionStrategy: When lockResolutionStrategy is set to SingleInstance and runMigration is set to true, the database lock applied by Liquibase is forcefully removed before the migration. This can solve problems where the application was shut down during migration, and the database remains locked.

    • Allowed values:
      • Not set (Default)
      • SingleInstance

Was this page helpful?

Thanks for your feedback!

Chat with us

Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.

Propose documentation improvements directly

Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.

We're sorry this page wasn't helpful. Let us know how we can make it better!

Chat with us

Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.

Create an issue

Create a new GitHub issue in this repository - submit technical feedback, draw attention to a potential documentation bug, or share ideas for improvement and general feedback.

Propose documentation improvements directly

Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.