From 431538cc315407824a4a27321641d507fb132b2f Mon Sep 17 00:00:00 2001 From: szymonsztuka Date: Fri, 6 Jul 2018 10:56:01 +0100 Subject: [PATCH] Added example command to create dummy JAR file with migration for upgrading Cordapp from OS to ENT. (#1187) --- docs/source/database-management.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/source/database-management.rst b/docs/source/database-management.rst index 1fa2f88378..c1b74b70c0 100644 --- a/docs/source/database-management.rst +++ b/docs/source/database-management.rst @@ -240,7 +240,8 @@ These are the steps: In case you don't specify the actual ``MappedSchema`` name, the tool will generate one SQL file for each schema defined in the CorDapp 4. Inspect the file(s) to make sure it is correct. This is a standard SQL file with some Liquibase metadata as comments. 5. Create a jar with the ``migration`` folder (by convention it could be named: ``originalCorDappName-migration.jar``), - and deploy this jar together with the CorDapp. + and deploy this jar together with the CorDapp, e.g. run the following command in the node base directory + ``jar cvf /path/to/node/cordapps/MyCordapp-migration.jar migration``. 6. To make sure that the new migration will be used, do a dry run with the database management tool and inspect the output file.