In previous article, we showed you the network topology and the function of each network component. In this step of application deployment, we will set up this topology using Fabric based tools and commands. We will cover the whole network setup with the following steps<\/p>\n\n\n\n
The first step will be to generate keys and certificates for every\norganization and its associated entities like peers and orderer so that it can\nbe used to sign\/verify as they communicate over the network. For this use case,\nas mentioned earlier, we will use ‘cryptogen’ tool to generate the necessary\ncertificates. The following command generates the x.509 based crypto files.<\/p>\n\n\n\n
OrdererOrgs:\n - Name: Orderer\n Domain: fte.com\n Specs:\n - Hostname: orderer\nPeerOrgs:\n - Name: Org1\n Domain: app.fte.com\n Template:\n Count: 2\n Users:\n Count: 2\n - Name: Org2\n Domain: bnk.com\n Template:\n Count: 2\n Users:\n Count: 2\n - Name: Org3\n Domain: shp.com\n Template:\n Count: 2\n Users:\n Count: 1\n<\/code><\/pre>\n\n\n\ncryptogen generate –config=.\/crypto-config.yaml<\/p>\n\n\n\n
The above command uses the ‘cryptogen’ tool that reads the\n‘crypto-config.yaml.’ file to generate the certificates. The ‘crypto-config.yaml’\nfile depicts our network topology in a declarative way. The following\nconfiguration shows the \u2018crypto-config.yaml.\u2019 file that has our orderer and\nthree organizations with peers and users. <\/p>\n\n\n\n
Peers and users are denoted by numbers (using Count<\/em> field) where you can specify how\nmany users and peers you would like to setup per organization. <\/p>\n\n\n\nGenerating\ntransaction configuration<\/a><\/h4>\n\n\n\nMoving ahead, we will create transaction configuration artifacts.\nThese are stated as below:<\/p>\n\n\n\n
- Genesis block<\/li>
- Channel transaction configuration<\/li><\/ul>\n\n\n\n
We will use \u2018configtxgen\u2019 tool to generate the above artifacts. The\nsaid tool will read the \u2018configtx.yaml.\u2019 file. The below configuration shows\nthe \u2018configtx.yaml.\u2019 file. <\/p>\n\n\n\n
Profiles:\n\n TradeFinanceOrdererGenesis:\n Orderer:\n <<: *OrdererDefaults\n Organizations:\n - *OrdererOrg\n Consortiums:\n TradeConsortium:\n Organizations:\n - *Org1\n - *Org2\n - *Org3\n \n TradeFinanceOrgsChannel:\n Consortium: TradeConsortium\n Application:\n <<: *ApplicationDefaults\n Organizations:\n - *Org1\n - *Org2\n - *Org3\n\nOrganizations:\n\n - &OrdererOrg\n Name: OrdererOrg\n ID: OrdererMSP\n MSPDir: crypto-config\/ordererOrganizations\/fte.com\/msp\n\n - &Org1\n Name: Org1FTE\n ID: Org1FTE\n MSPDir: crypto-config\/peerOrganizations\/app.fte.com\/msp\n\n AnchorPeers:\n - Host: peer0.app.fte.com\n Port: 7051\n\n - &Org2\n Name: Org2BNK\n ID: Org2BNK\n MSPDir: crypto-config\/peerOrganizations\/bnk.com\/msp\n AnchorPeers:\n - Host: peer0.bnk.com\n Port: 7051\n\n - &Org3\n Name: Org3SHP\n ID: Org3SHP\n MSPDir: crypto-config\/peerOrganizations\/shp.com\/msp\n AnchorPeers:\n - Host: peer0.shp.com\n Port: 7051\n\nOrderer: &OrdererDefaults\n\n OrdererType: solo\n Addresses:\n - orderer.fte.com:7050\n BatchTimeout: 5s\n BatchSize:\n MaxMessageCount: 5\n AbsoluteMaxBytes: 10 MB\n PreferredMaxBytes: 512 KB\n\n Kafka:\n Brokers:\n - 127.0.0.1:9092\n\n Organizations:\n\nApplication: &ApplicationDefaults\n\n Organizations:\n<\/code><\/pre>\n\n\n\nThe \u2018configtx.yaml\u2019 file consists of profiles for ordering service and\nchannel. The orderer profile named ‘TradeFinanceOrdererGenesis’ will define a\nconsortium of our three organizations. The channel profile\n‘TradeFinanceOrgsChannel’ will have a reference to this consortium and will\nalso imply that all the three organization’s signature will be required to\ncreate that channel. <\/p>\n\n\n\n
The \u2018configtx.yaml\u2019 file also contains\ninformation like the path to root certificates for our three organizations, the\nendorsing peer with endpoint details and orderer default settings. <\/p>\n\n\n\n
Genesis\nblock<\/a><\/h4>\n\n\n\nAs a first step, we will create a genesis block or the first block of\nthe transaction. It is also called a configuration block, which will describe\nour three peer organizations and an orderer stating their root certificates and\naccess policies. This block will initialize the blockchain network or channel.\nThe following command generates the genesis block<\/p>\n\n\n\n
configtxgen -profile TradeFinanceOrdererGenesis -outputBlock\n.\/channel-artifacts\/genesis.block<\/p>\n\n\n\n
The above command uses ordering service profile named ‘TradeFinanceOrdererGenesis’\nto generate \u2018genesis.block\u2019 file and place it in the \u2018channel-artifacts\u2019\nfolder. The \u2018genesis.block\u2019 file will be used to bootstrap the ordering\nservice.<\/p>\n\n\n\n
Channel\ntransaction configuration<\/a><\/h4>\n\n\n\nNext, we will generate channel transaction configuration file. This\nwill be used to create the channel for our network. The following command\ngenerates the channel transaction configuration file. <\/p>\n\n\n\n
configtxgen -profile TradeFinanceOrgsChannel -outputCreateChannelTx\n.\/channel-artifacts\/channel.tx -channelID tradechannel<\/p>\n\n\n\n
The above command uses channel profile named\n‘TradeFinanceOrgsChannel’ to generate \u2018channel.tx\u2019 configuration file and\nplaces it in the channel-artifacts folder. The said file will be used to create\nthe channel.<\/p>\n\n\n\n
Starting\nthe network<\/a><\/h4>\n\n\n\nWe will start the network by spinning up our nodes. To start these\nnodes, we will use docker images provided by Fabric runtime. Docker provides a consistent environment to work with different\nplatforms like OS\/Mac\/Windows. Moreover, with Docker, you could also port your\napplication on the cloud. We will spin up the following nodes:<\/p>\n\n\n\n
\n\n\n\nNote: We will\nonly show few docker code snippets here. To view the entire code, you can\ndownload it from the GitHub at https:\/\/github.com\/enterprise-blockchain-book\/first-edition\/blob\/master\/hyperledger-fabric\/base\/docker-trade-finance-base.yaml<\/a><\/em> <\/p>\n\n\n\n image: hyperledger\/fabric-orderer\n environment:\n - ORDERER_GENERAL_GENESISFILE=\/var\/hyperledger\/orderer\/orderer.genesis.block\n command: orderer\n volumes:\n - ..\/channel-artifacts\/genesis.block:\/var\/hyperledger\/orderer\/orderer.genesis.block\n ports:\n - 7050:7050\n<\/code><\/pre>\n\n\n\n
\n\n\n\nNode: Orderer (orderer.fte.com)<\/p>\n\n\n\n
Below is the short docker snippet:<\/p>\n\n\n\n
The above docker image will spin up the orderer container on port\n7050. The important thing to observe is that we have bootstrapped our orderer\nservice with the genesis block we created earlier. It means the configuration\nblock will be created on the orderer service startup. We also specify the path\nto root certificates and key here.<\/p>\n\n\n\n
Node: Peer0 of Org1FTE(peer0.app.fte.com) <\/p>\n\n\n\n
Below is the short docker snippet:<\/p>\n\n\n\n
image: hyperledger\/fabric-peer\n environment:\n - CORE_PEER_TLS_CERT_FILE=\/etc\/hyperledger\/fabric\/tls\/server.crt\n - CORE_PEER_TLS_KEY_FILE=\/etc\/hyperledger\/fabric\/tls\/server.key\n - CORE_PEER_TLS_ROOTCERT_FILE=\/etc\/hyperledger\/fabric\/tls\/ca.crt\n command: peer node start\n ports:\n - 7051:7051\n<\/code><\/pre>\n\n\n\nThe above docker image will spin up peer node container for the first\norganization. It will use 7051 as a host and container port. It also specifies\npath to crypto credentials used for signing and verification. The rest of the\npeer nodes will also use the same above docker image and environment, but each\nwill use different host port. The below are the details of other peer nodes:<\/p>\n\n\n\n
- Org1 MSP id: Org1FTE – peer1.app.fte.com –\n8051:7051<\/li>
- Org2 MSP id: Org2BNK – peer0.bnk.com – 9051:7051<\/li>
- Org2 MSP id: Org2BNK – peer1.bnk.com – 10051:7051<\/li>
- Org3 MSP id: Org3SHP – peer0.bnk.com – 11051:7051<\/li>
- Org3 MSP id: Org3SHP – peer1.bnk.com – 12051:7051<\/li><\/ul>\n\n\n\n
Once all the nodes are up and running, we will go\nahead and create the channel.<\/p>\n\n\n\n
Creating\nChannel<\/a><\/h4>\n\n\n\nThe channel creation process reads our previously generated channel\ntransaction configuration artifact to create the channel. The following command\ncreates the channel:<\/p>\n\n\n\n
peer channel create -o orderer.fte.com:7050 -c tradechannel -f\n.\/channel-artifacts\/channel.tx <\/p>\n\n\n\n
The above command reads our previously configured\nartifact \u2018channel.tx\u2019 and creates the channel with the channel name as\n\u2018tradechannel.’ The \u2018-c\u2019 flag is used to specify the channel name. The channel\nname can be any name of your choice. The \u2018-f\u2019 flag is used to specify the\nconfiguration file, in this case, it is \u2018channel.tx\u2019 we generated using\n\u2018configtxgen\u2019 tool. The command returns the genesis block named\n‘tradechannel.block.’ This block file is then used to make our peer nodes join\nthe ‘tradechannel’ channel.<\/p>\n\n\n\n
Joining\npeers to the channel<\/a><\/h4>\n\n\n\nOnce the channel is created, the peer nodes should formally join the\nchannel to participate in the transactions on that channel. The following\ncommand is used to onboard peers to the channel ‘tradechannel’.<\/p>\n\n\n\n
peer channel join -b tradechannel.block<\/p>\n\n\n\n
The above command is supplied with the channel\nblock file ‘tradefinance.block’ we created in the previous (create channel)\ncommand. The -b’ option is used to specify the channel block file. You could be\nwondering where the name of the peer node is provided for joining the\n\u2018tradechannel\u2019? The answer lies in the CORE_PEER_ADDRESS<\/em>\nenvironment variable. You have to set this environment variable with the value\nof peer node address that you wish to join. Since we have 6 peer nodes, we must\nrun this command six times and change the value of the CORE_PEER_ADDRESS<\/em> environment to point to the correct peer node\naddress each time we run the command. So, to join the first peer node from\nOrg1, set the CORE_PEER_ADDRESS<\/em>\nvariable to the value ‘peer0.app.fte.com:7051′ and run the above command. You\nthen update the environment variable to point to the second peer node of the\nOrg1, i.e., peer1.app.fte.com:7051’ and run the command. Similarly, you do this\nfor all the peer nodes in Org2 and Org3. This way you will have all the peers\nnow becoming part of the ‘tradechannel’ channel. In the next step, we will\ninstall the chaincode (smart contract) on all the peer nodes.<\/p>\n\n\n\nInstalling\nthe chaincode<\/a><\/h4>\n\n\n\nWe will now install our trade finance chaincode file ‘tradefinancecontract.go’\non every peer nodes. Peer node endorses and verifies transactions invoked using\nthe chaincode. The following command installs the chaincode in the peer node\nfile system:<\/p>\n\n\n\n
peer chaincode install -n tradefinancecc -v 1.0 -p\ngithub.com\/hyperledger\/fabric\/examples\/chaincode\/go\/tradecontract<\/p>\n\n\n\n
The above command will install the chaincode\nwhich is located in the path\n‘github.com\/hyperledger\/fabric\/examples\/chaincode\/go\/tradecontract’ and give it\na name as ‘tradefinancecc’. The path denoted is mapped to volume path on the\ndocker container. It points to ‘hyperledger-fabric\/chaincode\/tradecontract’ folder\nthat contains our chaincode file. The chaincode will be installed in the file\nsystem of the peer node. Peer node address can be specified by setting the CORE_PEER_ADDRESS<\/em> environment variable\nas stated in the previous step. Since we have six peer nodes, you must run this\ncommand six times with each time updating the said environment variable to\npoint to correct peer address. The ‘-n’ option is used to provide a name to\nchaincode, and ‘-p’ option is used to specify the source path of our chaincode\nfile. In the next step, we will instantiate this chaincode.<\/p>\n\n\n\nInstantiating\nthe chaincode<\/a><\/h4>\n\n\n\nNow, the chaincode ‘tradefinancecc’ is installed on each peer, we will\ninstantiate the same. Instantiating the chaincode means initializing the\nchaincode by invoking its init() method. The following command instantiates the\nchaincode:<\/p>\n\n\n\n
peer chaincode instantiate -o orderer.fte.com:7050 -C tradechannel\n-n tradefinancecc -v 1.0 -c ‘{“Args”:[“init”,”FTE_2″,”FTE_B_1″,”FTE_S_1″,”SKU001″,”10000″,”1000″]}’\n-P “OR (‘Org1FTE.member’,’Org2BNK.member’,’Org3SHP.member’)”<\/p>\n\n\n\n
The above command instantiates the chaincode on\nthe target peer (as mentioned in the CORE_PEER_ADDRESS<\/em>\nenvironment variable) and launches its own isolated docker container. The\ncommand uses Args<\/em> key field to pass\nthe function name ‘Init’<\/em> and various\nother parameters to initialize our trade finance smart contract. It also sets\nthe endorsing policy by specifying which organization peers will do the\nendorsement. The policy is specified using ‘-P’ option.<\/p>\n\n\n\nInvoking\nthe chaincode<\/a><\/h4>\n\n\n\nWith the chaincode instantiated in earlier step, we can now invoke\nbusiness methods. Invoking means calling the ‘Invoke’<\/em> method of the chaincode, which then calls the appropriate\nbusiness method based on the method name passed as a parameter to the command.\nThe following command invokes the \u2018createLOC\u2019 method of the chaincode.<\/p>\n\n\n\npeer chaincode invoke -o orderer.fte.com:7050 -C tradechannel -n\ntradefinancecc -c ‘{“Args”:[“createLOC”,”FTE_2″]}’<\/p>\n\n\n\n
The above command invokes the \u2018createLOC\u2019<\/em> method on the target peer\n(as mentioned in the CORE_PEER_ADDRESS<\/em>\nenvironment variable). You can point to any peer as transactions are invoked on\nall peers. If you recall, every peer maintains a copy of the ledger, and\ntherefore, all peer will execute the transaction. Once the chaincode is\ninstantiated or any business method is invoked, it starts the chaincode\ncontainers for all the peers. The above command executes \u2018createLOC\u2019<\/em> method by passing the trade id. The trade status is\nthen updated to the ledger. In the next step, we will query the state of the\nledger.<\/p>\n\n\n\nQuerying\nthe ledger<\/a><\/h4>\n\n\n\nNow, since we have executed one business method named \u2018createLOC’<\/em>, we will check if it indeed\nupdated the trade status. You can check the state of the ledger by giving the\nfollowing command:<\/p>\n\n\n\npeer chaincode query -C tradechannel -n mycc -c\n‘{“Args”:[“query”,”FTE_2″]}’<\/p>\n\n\n\n
The above command queries the channel by passing the trade id. The\nquery is executed on the target peer and returns the current state of the\nledger. If you view the log file of the container, you will see the trade\nstatus changed to ‘LOC created.’<\/p>\n\n\n\n