Starting a Corda node
The components to be started in a deployment are:
corda-firewall.jaris used by both Bridge and Float. The JAR file assumes the input is
bridge.confhowever this may be overridden with the
--config-fileparameter so you can designate whatever config file name you wish to use.
To start the Float run the following command from the Float VM:
/usr/bin/java -Xmx1024m -jar /opt/corda/corda-firewall-4.9.jar --config-file float.conf
You should see the following output:
FloatSupervisorService: active = false FloatSupervisorService: active = true
To start the Node run the following command from the Node VM:
/usr/bin/java -Xmx2048m -jar /opt/corda/corda-4.9.jar --config-file node.conf
If your node configuration file is obfuscated and you want to de-obfuscate it when running the node, you need to pass the obfuscation seed and passphrase to the node in the node run command.
To do so using the Configuration Obfuscator command-line tool, use the
--config-obfuscation-passphrase flags, respectively, in your node run command.
The following example shows how to pass a seed and a passphrase explicitly to a node component using the Configuration Obfuscator command-line tool:
$ /usr/bin/java -Xmx2048m -jar /opt/corda/corda-4.9.jar --config-file node.conf --config-obfuscation-seed my-seed --config-obfuscation-passphrase my-passphrase
To pass the seed and passphrase to a node using environment variables, follow the example below:
$ export CONFIG_OBFUSCATION_SEED=my-seed; export CONFIG_OBFUSCATION_PASSPHRASE=my-passphrase; /usr/bin/java -Xmx2048m -jar /opt/corda/corda-4.9.jar --config-file node.conf
All flows can be paused when the node starts up - you can enable this in one of the following ways:
- Use the command-line option
- Add the
smmStartMode="Safe"option to the node configuration file.
These flows can then be individually retried via RPC or the node shell.
See Pause and resume flows for more information.
To start the Bridge run the following command from the Bridge VM:
/usr/bin/java -Xmx1024m -jar /opt/corda/corda-firewall-4.9.jar
You should see the following output in the Bridge:
BridgeSupervisorService: active = false BridgeSupervisorService: active = true
You should see the following output in the Float log:
Now listening for incoming connections on VM-Of-Float-Public-IP:Port
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
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.