2017-06-05 12:37:23 +00:00
|
|
|
Running a node
|
2017-01-06 11:05:37 +00:00
|
|
|
==============
|
2016-08-23 09:25:06 +00:00
|
|
|
|
2016-11-25 14:29:13 +00:00
|
|
|
Starting your node
|
2016-08-23 09:25:06 +00:00
|
|
|
------------------
|
|
|
|
|
|
2017-07-21 11:33:31 +00:00
|
|
|
After following the steps in :doc:`deploying-a-node`, you should have deployed your node(s) with any chosen CorDapps
|
|
|
|
|
installed. You run each node by navigating to ``<node_dir>`` in a terminal window and running:
|
2016-08-23 09:25:06 +00:00
|
|
|
|
2017-03-21 13:45:18 +00:00
|
|
|
.. code-block:: shell
|
|
|
|
|
|
|
|
|
|
Windows: java -jar corda.jar
|
|
|
|
|
UNIX: ./corda.jar
|
2016-08-23 09:25:06 +00:00
|
|
|
|
|
|
|
|
.. warning:: If your working directory is not ``<node_dir>`` your plugins and configuration will not be used.
|
|
|
|
|
|
2017-07-21 11:33:31 +00:00
|
|
|
The configuration file and workspace paths can be overridden on the command line. For example:
|
2016-08-31 08:48:19 +00:00
|
|
|
|
2017-03-21 13:45:18 +00:00
|
|
|
``./corda.jar --config-file=test.conf --base-directory=/opt/r3corda/nodes/test``.
|
2016-08-31 08:48:19 +00:00
|
|
|
|
2017-01-06 19:38:48 +00:00
|
|
|
Otherwise the workspace folder for the node is the current working path.
|
2016-08-31 08:48:19 +00:00
|
|
|
|
2016-11-25 14:29:13 +00:00
|
|
|
Debugging your node
|
2016-09-23 09:55:40 +00:00
|
|
|
-------------------
|
2016-08-31 08:48:19 +00:00
|
|
|
|
2017-07-21 11:33:31 +00:00
|
|
|
To enable remote debugging of the node, run the following from the terminal window:
|
2016-08-31 08:48:19 +00:00
|
|
|
|
|
|
|
|
``java -Dcapsule.jvm.args="-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=5005" -jar corda.jar``
|
|
|
|
|
|
|
|
|
|
This command line will start the debugger on port 5005 and pause the process awaiting debugger attachment.
|
|
|
|
|
|
2017-07-21 11:33:31 +00:00
|
|
|
Viewing the persisted state of your node
|
|
|
|
|
----------------------------------------
|
2016-10-04 18:01:09 +00:00
|
|
|
|
|
|
|
|
To make examining the persisted contract states of your node or the internal node database tables easier, and providing you are
|
|
|
|
|
using the default database configuration used for demos, you should be able to connect to the internal node database over
|
|
|
|
|
a JDBC connection at the URL that is output to the logs at node start up. That URL will be of the form ``jdbc:h2:tcp://<host>:<port>/node``.
|
|
|
|
|
|
|
|
|
|
The user name and password for the login are as per the node data source configuration.
|
|
|
|
|
|
|
|
|
|
The name and column layout of the internal node tables is in a state of flux and should not be relied upon to remain static
|
|
|
|
|
at the present time, and should certainly be treated as read-only.
|
|
|
|
|
|
2017-01-18 12:42:22 +00:00
|
|
|
.. _CordaPluginRegistry: api/kotlin/corda/net.corda.core.node/-corda-plugin-registry/index.html
|
|
|
|
|
.. _PluginServiceHub: api/kotlin/corda/net.corda.core.node/-plugin-service-hub/index.html
|
2017-07-21 11:33:31 +00:00
|
|
|
.. _ServiceHub: api/kotlin/corda/net.corda.core.node/-service-hub/index.html
|
