Record'in network nodes configuration

Step by step configuration of Record'in for implementing network nodes

This shows all recommended steps for installation of Record'in software.


The same documentation in PDF format.


I.Introduction

This document describes the configuration procedure of Record’in software to implement a network with several Blockchain nodes.



II.Installer

 

Name Company/Role Signature Initials Date
Philippe Schweitzer Recordins/CEO
PHS 03/03/19


III.System Information

Attribute Value
Hostname demo1.recordins.com
demo2.recordins.com
Target Server Virtual machine
Server Function VM for development
Application Name Record’in 19-01
Version 19-01
Manufacturer Recordins
Distribution Media Electronic / Internet
Language English
Data source provided by Recordins
Comment N/A



Conventions :

N/A


IV.Prerequisites

No. Prerequisite Prerequisite met Y/N
1 A set of Recordin nodes installed using the procedure found at this page:

https://www.recordins.com/r/xpi



V.Installation steps


No. Activity Succesfully Completed Y/N
1 Before starting, we must choose one node as the source for initiating the blockchain of the other nodes.
The chosen node will have no special properties after the operation, and will continue to work a usual, like any other node of the network.

For the example, we will select the “demo1.recordins.com” as the source node and “demo2.recordins.com” to materialize the other nodes. Note that here the process only shows how to connect 2 nodes together, but in fact just follow the same process as for the “demo2.recordins.com” in order to configure the rest of the other nodes.

For each of the nodes, including the source one, make sure having executed them at least once, each of them, even in standalone mode. This in order to generate their unique node ID.

For each of them, connect, and go to the folder “/soft/recordin/database” and get the value of “nodeId” property inside the “nodeId.properties” file.

Once having collected all the nodes id, build one string chain like following:
PeerActive=[{ url = "enode://<nodeid>@<hostname>:<port>" }, { url = "enode://<nodeid>@<hostname>:<port>" }]

The port number must be the same for all nodes, and can be found inside the “etc/recordin.properties” file, the value found for the “PeerListenPort” property.

For instance we can build following string for the demo nodes, take care to remove line breaks before saving the configuration file:
PeerActive=[
{url="enode://2123840ab0f05f85ae7bd1f94f4e60b56585e0f35045d62eeb1b298bc8fcff70dd2aa4b85fcede5b13abba7066d0f958683fc0addc54c97ae2694b3cd8d23a9d@demo1.recordins.com:50000" },
{url="enode://ea6a4b8e793a33f2024270c86409e7787212a6dcad025b50f4577fec4b6044f506c5a4a835201e308c5808e9b2829a7c8ed67b003cefe0430997d1acc0a16c15@demo2.recordins:50000" }
]

2 Connect with ssh as root to the source node

The first password is provided by your administrator

$> ssh root@<hostname in section 3>

3 This is to update of the source node chosen at step 1, bypass this step if you are configuring another node

Stop the chosen blockchain node
systemctl stop recordin
vim /soft/recordin/etc/recordin.properties

Set value to 'false' for property "NodeStandalone" :
NodeStandalone=false

Set the string built at step 1 for the property “PeerActive”, for instance in our example:
PeerActive=[{url="enode://2123840ab0f05f85ae7bd1f94f4e60b56585e0f35045d62eeb1b298bc8fcff70dd2aa4b85fcede5b13abba7066d0f958683fc0addc54c97ae2694b3cd8d23a9d@demo1.recordins.com:5000" },{url="enode://ea6a4b8e793a33f2024270c86409e7787212a6dcad025b50f4577fec4b6044f506c5a4a835201e308c5808e9b2829a7c8ed67b003cefe0430997d1acc0a16c15@demo2.recordins:5000"}]

Eventually if required, change value of property "PeerNetworkId" :
PeerNetworkId=<ID of your network>

Remove following files and folders if they are existing:
rm -rf /soft/recordin/etc/keys.properties 2>/dev/null
rm -rf /soft/recordin/etc/users.properties 2>/dev/null
rm -rf /soft/recordin/database-recordin-private-network-standard 2>/dev/null

Retart the blockchain node
systemctl restart recordin

4 This is to update of the other nodes chosen at step 1, return to the step 2 if you are configuring the source node
Before starting with other nodes, make sure the source node ends loading, and had printed following in its log file:
….. [startPlatform] INFO com.recordins.recordin.Main - Recordin started
Stop the blockchain node
systemctl stop recordin
vim /soft/recordin/etc/recordin.properties

Set value to 'false' for property "NodeStandalone" :
NodeStandalone=false

Set the string built at step 1 for the property “PeerActive”, for instance in our example:
PeerActive=[{url="enode://2123840ab0f05f85ae7bd1f94f4e60b56585e0f35045d62eeb1b298bc8fcff70dd2aa4b85fcede5b13abba7066d0f958683fc0addc54c97ae2694b3cd8d23a9d@demo1.recordins.com:5000" },{url="enode://ea6a4b8e793a33f2024270c86409e7787212a6dcad025b50f4577fec4b6044f506c5a4a835201e308c5808e9b2829a7c8ed67b003cefe0430997d1acc0a16c15@demo2.recordins:5000"}]

Eventually if required, change value of property "PeerNetworkId" :
PeerNetworkId=<ID of your network>

Remove following files and folders if they are existing:
rm -rf /soft/recordin/etc/keys.properties 2>/dev/null
rm -rf /soft/recordin/etc/users.properties 2>/dev/null
rm -rf /soft/recordin/database-recordin-private-network-standard 2>/dev/null

5 This is to update of the other nodes chosen at step 1, return to the step 2 if you are configuring the source node

Still on the other nodes chosen at step 1
Create a file having the admin user password, and put following content. By default the admin password is password.
Please refer to the nodes configuration guide in order to update the administrator password on all nodes

vim /soft/recordin/etc/users.properties
---
admin=password
---

Restart the blockchain nodes


6
Repeat steps 3 and 4 for all other nodes chosen at step 1
systemctl restart recordin


VI.Validation / Installation Qualification steps

No. Activity
1 Action (on each nodes):

http://<hostname in section 3>:8080
OR with SSL:
http://<hostname in section 3>
Expected results:

Record’in’s page opens correctly, and menu “Admin>User” opens without error.

Select the “Admin” user (just click on its row).
Then on the right panel click on the “Display system attributes” button and verify that the user has the same “UID” on each nodes.