ExternalVendorCode/corda
1
0
Fork 0
mirror of https://github.com/corda/corda.git synced 2025-03-14 00:06:45 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Document database configuration step when deploying nodes remotely, related to ENT-1678(#1224)

Browse Source
This commit is contained in:
szymonsztuka 2018-07-09 16:14:18 +01:00 committed by GitHub
parent e863683c6c
commit 7e7ea3bab7
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 11 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/source/generating-a-node.rst
View File

@ -123,6 +123,9 @@ Following the previous example ``PartyB`` node will have additional configuratio
}
}
Additional properties can be also specified directly by the ``extraConfig`` property which defines a map of keys and values. The example config above uses ``extraConfig`` to set value of the ``jvmArgs`` property.
See the extended example of :ref:`adding database configuration <testing_cordform_ref>`.
Cordform parameter `drivers` of the `node` entry lists paths of the files to be copied to the `./drivers` subdirectory of the node.
To copy the same file to all nodes `ext.drivers` can be defined in the top level and reused for each node via `drivers=ext.drivers``.

10
docs/source/running-a-node.rst
View File

@ -130,7 +130,13 @@ To create nodes locally and run on a remote machine perform the following steps:
2. Copy the generated directory structure to a remote machine using e.g. Secure Copy.
3. Optionally, bootstrap the network on the remote machine.
3. Optionally, add database configuration settings if they weren't specified in the first step.
This step needs to be performed if the local machine doesn't have access to the remote database (a database couldn't be configured in the first step).
In each top level ``[NODE NAME]_node.conf`` configuration file add the database settings and copy the JDBC driver JAR (if required).
Edit the top level ``[NODE NAME]_node.conf`` files only and not the files (``node.conf``) inside the node subdirectories.
4. Optionally, bootstrap the network on the remote machine.
This is optional step when a remote machine doesn't accept ``localhost`` addresses, or the generated nodes are configured to run on another host's IP address.
@ -140,7 +146,7 @@ To create nodes locally and run on a remote machine perform the following steps:
``java -jar corda-tools-network-bootstrapper-Master.jar --dir <nodes-root-dir>``
4. Run nodes on the remote machine using :ref:`runnodes command <starting-all-nodes-at-once>`.
5. Run nodes on the remote machine using :ref:`runnodes command <starting-all-nodes-at-once>`.
The above steps create a test deployment as ``deployNodes`` Gradle task would do on a local machine.