Blockchain Hyperledger With Fabric CA, Fabric, Explorer, Raft, Chaincode and Monitoring

Establishing a corporate blockchain network in a productive environment has some challenges that must be solved by blockchain solution architects. This repository was organized from our experience in creating blockchain environments, quality and productive, for a software system that uses blockchain as a data storage solution in its backend to execute a decentralized and distributed multi-organization business process.

The source-code will focus on how the blockchain architect may use sources to configure the Hyperledger frameworks together, Fabric CA + Fabric + Explorer, on a network with multiple Raft orderers, and how to guide the developmentto establish resources that can provide the monitoring over the blockchain components of organization, as well as the verification of each chaincode that is published in the system.

Steps

1. Configure TLSR CA and create users at TlsRing organization:
   1. Startup TLSR CA: rca.tlsring.blockchain.biz;
   2. Configure TLSR CA running scripts;
   3. Register and enroll users at TLSR CA;
   4. Stay with TLSR CA on-line/loaded.
2. Prepare Coffee organization with PEER components:
   1. Configure RCA at Coffee organization and create users:
      1. Startup RCA: rca.coffee.blockchain.biz, running 'rca-init.sh';
      2. Configure RCA running scripts;
      3. Register and enroll users at RCA;
      4. Enroll users at TLSR CA;
      5. Shutdown RCA, running 'rca-stop.sh'.
   2. Startup Coffee organization components:
      1. Running 'srv-init.sh';
      2. Verify status running 'srv-check-status.sh';
      3. You may (or not) shutdown organization components, running 'srv-stop.sh'.
3. Prepare Juice organization with PEER components:
   1. Configure RCA at Juice organization and create users:
      1. Startup RCA: rca.juice.blockchain.biz, running 'rca-init.sh';
      2. Configure RCA running scripts;
      3. Register and enroll users at RCA;
      4. Enroll users at TLSR CA;
      5. Shutdown RCA, running 'rca-stop.sh';
   2. Startup Juice organization components:
      1. Running 'srv-init.sh';at TlsRing organization
      2. Verify status running 'srv-check-status.sh';
      3. You may (or not) shutdown organization components, running 'srv-stop.sh'.
4. Prepare Trading organization with ORDERER components:
   1. Configure RCA at Trading organization and create users:
      1. Startup RCA: rca.trading.blockchain.biz, running 'rca-init.sh';
      2. Configure RCA running scripts;
      3. Register and enroll users at RCA;
      4. Enroll users at TLSR CA;
      5. Shutdown RCA, running 'rca-stop.sh'.
5. Stop TLSR CA at TlsRing organization:
   1. Shutdown TLSR CA container.
6. Genesis:
   1. Inspect the file './configtx/confitx.yaml.
   2. Generate genesis block to run system channel, named syschannel:
      1. Run the file '1-generate-genesis-block.sh';
      2. Verify the file "genesis.block" created at "./config" folder.
   3. Generate genesis transaction block to run development channel, named devchannel:
      1. Run the file '2-generate-genesis-tx.sh';
      2. Verify the file "devchanneltrack.tx" created at "./config" folder.
7. Start Orderers
   1. Move to Trading organization;
   2. Startup components, running 'ordering-init.sh';
   3. Verify status running 'ordering-check-status.sh'.

END

End