Upgrading a Corda (open source) Node to Corda Enterprise

Upgrading the version of Corda on a node

CorDapps, contracts and states written for Corda 3.x and Corda 4.x are compatible with Corda Enterprise 4.0, so upgrading existing open source Corda nodes should be a simple case of updating the Corda JAR. For developer information on recompiling CorDapps against Corda Enterprise, see upgrade-notes.

Upgrading the Node

See Upgrading your node to Corda 4 for general instructions on upgrading your node.

Database upgrades

When upgrading an existing node from Corda 3.x or Corda 4.x to Corda Enterprise, the node operator has the option of using one of the enterprise database engines that are supported (see Node database). We highly recommend moving away from the default H2 database when setting up a production node.

Corda Enterprise uses Liquibase for database schema management. See Database management for more info.

Migrating existing data from a Corda 4.0 H2 database to a Corda Enterprise 4.0 supported database

The procedure for migrating from H2 to a commercial database is as follows:

Migrating existing data from a Corda 3.3 H2 database to a Corda Enterprise 4.0 supported database

Update Corda (open source) 3.3 node to Corda (open source) Corda Enterprise 4.0 node first. Then follow the procedure migration from H2 database.

Migrating existing data from a Corda 3.0, 3,1 or 3.2 H2 database to a Corda Enterprise 4.0 supported database

Please ensure you follow the instructions in Upgrade Notes to upgrade your database to the latest minor release of Corda (3.3 as time of writing), and then proceed with upgrading following the instructions above