Adjust deployment notes

- update to new config
This commit is contained in:
Wawrzyniec Niewodniczański 2019-01-08 14:09:55 +00:00
parent 29a17d9de4
commit 4eb7114134

View File

@ -14,7 +14,7 @@ handling, and ensures the Corda service is run at boot.
**Prerequisites**: **Prerequisites**:
* Oracle Java 8. The supported versions are listed in :doc:`getting-set-up` * Supported Java 8. The supported versions are listed in :doc:`getting-set-up`
1. As root/sys admin user - add a system user which will be used to run Corda: 1. As root/sys admin user - add a system user which will be used to run Corda:
@ -66,13 +66,8 @@ handling, and ensures the Corda service is run at boot.
* Change the ports if necessary, for example if you are running multiple nodes on one server (see below). * Change the ports if necessary, for example if you are running multiple nodes on one server (see below).
* Enter an email address which will be used as an administrative contact during the registration process. This is * Enter an email address which will be used as an administrative contact during the registration process. This is
only visible to the permissioning service. only visible to the permissioning service.
* Enter your node's desired legal name. This will be used during the issuance of your certificate and should rarely * Enter your node's desired legal name (see :ref:`node-naming` for more details).
change as it should represent the legal identity of your node. * Setup RPC users (*optional*).
* Organization (``O=``) should be a unique and meaningful identifier (e.g. Bank of Breakfast Tea)
* Location (``L=``) is your nearest city
* Country (``C=``) is the `ISO 3166-1 alpha-2 code <https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2>`_
* Change the RPC username and password.
.. note:: Ubuntu 16.04 and most current Linux distributions use SystemD, so if you are running one of these .. note:: Ubuntu 16.04 and most current Linux distributions use SystemD, so if you are running one of these
distributions follow the steps marked **SystemD**. distributions follow the steps marked **SystemD**.
@ -190,7 +185,7 @@ at boot, and means the Corda service stays running with no users connected to th
**Prerequisites**: **Prerequisites**:
* Oracle Java 8. The supported versions are listed in :doc:`getting-set-up` * Supported Java 8. The supported versions are listed in :doc:`getting-set-up`
1. Create a Corda directory and download the Corda jar. Replace ``VERSION_NUMBER`` with the desired version. Here's an 1. Create a Corda directory and download the Corda jar. Replace ``VERSION_NUMBER`` with the desired version. Here's an
example using PowerShell:: example using PowerShell::
@ -214,15 +209,12 @@ at boot, and means the Corda service stays running with no users connected to th
keyStorePassword = "cordacadevpass" keyStorePassword = "cordacadevpass"
trustStorePassword = "trustpass" trustStorePassword = "trustpass"
devMode = false devMode = false
rpcUsers = [ rpcSettings {
{ useSsl = false
user=corda standAloneBroker = false
password=portal_password address = "example.com:10003"
permissions=[ adminAddress = "example.com:10004"
ALL
]
} }
]
custom { jvmArgs = [ '-Xmx2048m', '-XX:+UseG1GC' ] } custom { jvmArgs = [ '-Xmx2048m', '-XX:+UseG1GC' ] }
4. Make the following changes to ``C:\Corda\node.conf``: 4. Make the following changes to ``C:\Corda\node.conf``:
@ -233,13 +225,8 @@ at boot, and means the Corda service stays running with no users connected to th
* Change the ports if necessary, for example if you are running multiple nodes on one server (see below). * Change the ports if necessary, for example if you are running multiple nodes on one server (see below).
* Enter an email address which will be used as an administrative contact during the registration process. This is * Enter an email address which will be used as an administrative contact during the registration process. This is
only visible to the permissioning service. only visible to the permissioning service.
* Enter your node's desired legal name. This will be used during the issuance of your certificate and should rarely * Enter your node's desired legal name (see :ref:`node-naming` for more details).
change as it should represent the legal identity of your node. * Setup RPC users (*optional*).
* Organization (``O=``) should be a unique and meaningful identifier (e.g. Bank of Breakfast Tea)
* Location (``L=``) is your nearest city
* Country (``C=``) is the `ISO 3166-1 alpha-2 code <https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2>`_
* Change the RPC username and password.
5. Copy the required Java keystores to the node. See :doc:`permissioning` 5. Copy the required Java keystores to the node. See :doc:`permissioning`
@ -253,7 +240,6 @@ at boot, and means the Corda service stays running with no users connected to th
nssm install cordanode1 C:\ProgramData\Oracle\Java\javapath\java.exe nssm install cordanode1 C:\ProgramData\Oracle\Java\javapath\java.exe
nssm set cordanode1 AppDirectory C:\Corda nssm set cordanode1 AppDirectory C:\Corda
nssm set cordanode1 AppParameters "-Xmx2048m -jar corda.jar --config-file=C:\corda\node.conf"
nssm set cordanode1 AppStdout C:\Corda\service.log nssm set cordanode1 AppStdout C:\Corda\service.log
nssm set cordanode1 AppStderr C:\Corda\service.log nssm set cordanode1 AppStderr C:\Corda\service.log
nssm set cordanode1 Description Corda Node - Bank of Breakfast Tea nssm set cordanode1 Description Corda Node - Bank of Breakfast Tea
@ -263,7 +249,6 @@ at boot, and means the Corda service stays running with no users connected to th
9. Modify the batch file: 9. Modify the batch file:
* If you are installing multiple nodes, use a different service name (``cordanode1``) for each node * If you are installing multiple nodes, use a different service name (``cordanode1``) for each node
* Set the amount of Java heap memory available to this node by modifying the -Xmx argument
* Set an informative description * Set an informative description
10. Provision the required certificates to your node. Contact the network permissioning service or see 10. Provision the required certificates to your node. Contact the network permissioning service or see