Node folder structure
A folder containing a Corda node files has the following structure:
. ├── additional-node-infos // Additional node infos to load into the network map cache, beyond what the network map server provides ├── artemis // Stores buffered P2P messages ├── brokers // Stores buffered RPC messages ├── certificates // The node's certificates ├── corda-webserver.jar // The built-in node webserver (DEPRECATED) ├── corda.jar // The core Corda libraries (This is the actual Corda node implementation) ├── cordapps // The CorDapp JARs installed on the node ├── drivers // Contains a Jolokia driver used to export JMX metrics, the node loads any additional JAR files from this directory at startup. ├── logs // The node's logs ├── network-parameters // The network parameters automatically downloaded from the network map server ├── node.conf // The node's configuration files ├── persistence.mv.db // The node's database (present when the node uses the embedded H2 database instance) └── shell-commands // Custom shell commands defined by the node owner
You install CorDapps on the node by placing CorDapp JARs in the
In development mode (i.e. when
devMode = true), the
certificates directory is filled with pre-configured
keystores if they do not already exist to ensure that developers can get the nodes working as quickly as
The keystores store the key pairs and certificates under the following aliases:
nodekeystore.jksuses the aliases
sslkeystore.jksuses the alias
All the keystores use the password provided in the node’s configuration file using the
If no password is configured, it defaults to
To learn more, see Network certificates .
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.