-
Notifications
You must be signed in to change notification settings - Fork 155
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix typos in README Basic/tutorial-networkbootstrapper
- Loading branch information
Showing
1 changed file
with
8 additions
and
8 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,15 +1,15 @@ | ||
# Network Bootstrapper Tutorial | ||
|
||
In this tutorial, we will walk through the steps of bootstrapping a Corda Network using the Corda Network Bootstrapper. This tutorial consits of three node Config files and 2 shell scripts to ease up the manual copying of the files and folders. | ||
In this tutorial, we will walk through the steps of bootstrapping a Corda Network using the Corda Network Bootstrapper. This tutorial consists of 3 node Config files and 2 shell scripts to ease up the manual copying of the files and folders. | ||
|
||
Due to the size cap of the github uploaded file, you will need to manually download the Corda Network Bootstrapper (to this directory). The download link is at [here](https://software.r3.com/ui/native/corda-releases/net/corda/corda-tools-network-bootstrapper) | ||
Due to the size cap of the GitHub uploaded file, you will need to manually download the Corda Network Bootstrapper (to this directory). The download link is at [here](https://software.r3.com/ui/native/corda-releases/net/corda/corda-tools-network-bootstrapper) | ||
|
||
## Deploy a local Corda Network via the bootstrapper | ||
## Deploy a local Corda Network via the bootstrapper | ||
With the Corda Network Bootstrapper downloaded to this directory, you can simply call: (with the version name of the bootstrapper that you downloaded) | ||
``` | ||
java -jar corda-tools-network-bootstrapper-4.9.jar | ||
``` | ||
This command will gennerate the node folders that correspondes with each node config file. You should expect some folder structure like this: | ||
This command will generate the node folders that corresponds with each node config file. You should expect some folder structure like this: | ||
``` | ||
. | ||
├── network_Bootstrapper.jar | ||
|
@@ -30,9 +30,9 @@ Next, you will need to go into each node folder and start the node. | |
cd PA | ||
java -jar corda.jar | ||
``` | ||
Then, you can go into the PB folder and Notary folder to do the same steps, and you will have a Corda network running on your local machine. | ||
Then, you can go into the PB folder and Notary folder to do the same steps, and you will have a Corda network running on your local machine. | ||
|
||
## Deploy a Corda Network onto VMs via the bootstrapper | ||
## Deploy a Corda Network onto VMs via the bootstrapper | ||
|
||
When deploying a Corda network to remote VMs, you would need to do an additional step before bootstrap the node folders. You would need to go into the node.conf file and add the VM address. For example: (this is not the full config file, you still need other fields.) | ||
``` | ||
|
@@ -45,11 +45,11 @@ rpcSettings { | |
useSsl=false | ||
} | ||
``` | ||
After change the p2pAddress, you can now perform the bootstrapping with | ||
After change the p2pAddress, you can now perform the bootstrapping with | ||
``` | ||
java -jar corda-tools-network-bootstrapper-4.9.jar | ||
``` | ||
Next, we need to drop the node folder to the remote VMs. I simply use the `scp` command. For example: | ||
Next, we need to drop the node folder to the remote VMs. I simply use the `scp` command. For example: | ||
``` | ||
scp -r ./PartyA [email protected]:./ | ||
``` | ||
|