Installing Hyperledger Fabric

Make sure you've done all the Prerequisites 

Network Architecture

• 1 Orderer
• 1 Organization
• 3 peers
• 3 couchdb for each peer
• 1 ca
• 1 cli (Optional)

Setup the Network

1. Set the GOPATH. You can do this by adding this line to your /etc/environment (for a system-wide installation) or $HOME/.bashprofile : export GOPATH=/usr/local/go. Source if you set this in the same linux sesison then, source /etc/environment (OR)  source $HOME/.bashprofile
2. git clone of Solo Orderer Network:    git clone -b SoloOrdererNetwork https://github.com/TheCognizantFoundry/Insights.git
3. cd hyperledger-fabric-basic-network

4. Configuration: Values like DOMAIN, CHANNEL_NAME, FABRIC_VERSION, TIME_ZONE,etc ... can be modified in .env file based on your requirement.

   .env

   FABRIC_VERSION=<hyperledger_fabric_version>
   COMPOSE_PROJECT_NAME=<your_project_name>
   DOMAIN=<your_company.com>
   CHANNEL_NAME=<channelname>
   CHANNEL_FILE_NAME=<channel_transaction_filename.tx>
   GENESIS_FILE_NAME=<genesis_filename.block>
   CHANNEL_ARTIFACTS_PATH=<folder_path_for_storing_artifacts>
   CA_USER_ENROLLMENT=<admin_username_to_be_enrolled>
   CA_ENROLLMENT_SECRET=<admin_password>
   TIME_ZONE=<Continent/City>

5. Provide executable permissions to sh files:  chmod +x *.sh
6. Start network for the first time. 

   network.sh - Generate the crypto-material, start/stop/restart the network.

   ./network.sh -m download

   ./network.sh -m up

7. Start for the first time:

8. Start/Stop the Network :

    ./network.sh -m start./network.sh -m stop

9. Recreate the containers without losing the data.

    ./network.sh -m recreate

10. Clean and Remove the Network.

     ./network.sh -m down

11. Verify if all the docker containers are running

    docker ps
12. ./network.sh itself will create and join the channel for Anchor peer - peer0.   

      Optional Step for information: Create and Join channel in Anchor peer - peer0.org1 :

      Get into peer0.org1 container: docker exec -it peer0.org1.<DOMAIN> bash

      Create: peer channel create -o orderer.<DOMAIN>:7050 -c mychannel -f /var/hyperledger/configs/channel.tx

      Join: peer channel join -o orderer.<DOMAIN> -b mychannel.block
13. Fetch the block and join channel in other peers: 

    Get into peer0.org1 container: docker exec -it peer0.org1.<DOMAIN> bash

    
    

    Fetch block: peer channel fetch 0 mychannel.block --channelID mychannel --orderer orderer.<DOMAIN>:7050

    Join channel: peer channel join -o orderer.<DOMAIN> -b mychannel.block

14. Install,Instantiate the chaincode in Anchor peer - peer0. Get into respective peer containers and use the below install command to install chaincode in other peers.

      Get into peer0.org1 container: docker exec -it peer0.org1.<DOMAIN> bash

      Install: peer chaincode install -n insightsAuditing -p /chaincode/src/nodejs -l node -v 1.0

    1. If your network is in dev mode (To find the mode of your network, go to docker-compose-base/docker-compose-base.yaml and search for "peer node". If the command used is "peer node start --peer-chaincodedev=true" then you are in dev mode) 

       1. Go into cli container: docker exec -it cli bash

       2. Execute the following command to run the chaincode in dev mode (Ensure the chaincode name and peer0 port is correct) :

          CORE_CHAINCODE_ID_NAME="insightsAuditing:1.0" node --inspect tool_chaincode.js --peer.address grpc://peer0.org1.<DOMAIN>:7052

       3. Get into peer0.org1 container: docker exec -it peer0.org1.<DOMAIN> bash and execute the following command:

Instantiate: peer chaincode instantiate -n insightsAuditing -v 1.0 -c '{"Args":["init"]}' -C mychannel

b. If your network is in prod mode (To find the mode of your network, go to docker-compose-base/docker-compose-base.yaml and search for "peer node". If the command used is "peer node start" then you are in prod mode)

Instantiate: peer chaincode instantiate -n insightsAuditing -v 1.0 -c '{"Args":["init"]}' -C mychannel

15. Get into ca container. Create user to connect from fabric sdk by using admin. Fabric sdk network connection requires the user's cert details to get connected to the fabric network.

docker exec -it ca.org1.<DOMAIN> bash

fabric-ca-client enroll -u http://Admin:<password>@localhost:7054

fabric-ca-client register -u "http://localhost:7054" --id.name "newusername" --id.secret "password" --id.type "client" --id.affiliation "org1.department1"

fabric-ca-client enroll -u "http://newusername:password@localhost:7054"

16. Test the Chaincode. Either insert record manually or let the data gets inserted via PlatformAuditEngine. Then, query as shown below. Modify ASSET-ID with your Asset ID value.

  Query: peer chaincode query -n insightsAuditing -c '{"Args":["GetAssetDetails","ASSET-ID"]}' -C mychannel

Make sure you've done all the Prerequisites 

Network Architecture

• 3 Orderers
• 2 Organizations
• 4 peers, 2 for each organization
• 4 couchdb for each peer
• 2 ca, 1 for each organization
• 4 Kafka broker instances
• 3 Zookeper instances
• 1 cli (Optional)

Setup the Network

1. Set the GOPATH. You can do this by adding this line to your /etc/environment (for a system-wide installation) or $HOME/.bashprofile : export GOPATH=/opt/gopath Source if you set this in the same linux sesison then, source /etc/environment (OR)  source $HOME/.bashprofile
2. Keep the hyperledger fabric source under GOPATH. 

   cd $GOPATH/src/github.com/
   mkdir hyperledger
   cd hyperledger
   git clone https://github.com/hyperledger/fabric.git
   
   

3. git clone of Kafka Fabric Network:   git clone -b KafkaFabricNetwork https://github.com/TheCognizantFoundry/Insights.git
4. cd Hyperledger_fabric_kafka

5. Configuration: Values like DOMAIN, CORE_PEER configs,etc ... can be modified in .env file based on your requirement.

   .env

   COMPOSE_PROJECT_NAME=<name_of_your_network>
   CONFIGTX_ORDERER_BATCHSIZE_MAXMESSAGECOUNT=10
   CONFIGTX_ORDERER_BATCHTIMEOUT=2s
   KAFKA_DEFAULT_REPLICATION_FACTOR=3
   CORE_LOGGING_GOSSIP=WARNING
   ORDERER_GENERAL_TLS_ENABLED=false
   ORDERER_GENERAL_TLS_PRIVATEKEY=/var/hyperledger/tls/server.key
   ORDERER_GENERAL_TLS_CERTIFICATE=/var/hyperledger/tls/server.crt
   ORDERER_TLS_CLIENTAUTHREQUIRED=false
   CORE_PEER_TLS_ENABLED=false
   CORE_PEER_TLS_CERT_FILE=/var/hyperledger/tls/server.crt
   CORE_PEER_TLS_KEY_FILE=/var/hyperledger/tls/server.key
   CORE_PEER_TLS_CLIENTAUTHREQUIRED=false
   CORE_PEER_GOSSIP_ORGLEADER_PEER0_ORG1=false
   CORE_PEER_GOSSIP_USELEADERELECTION_PEER0_ORG1=true
   CORE_PEER_GOSSIP_ORGLEADER_PEER0_ORG2=false
   CORE_PEER_GOSSIP_USELEADERELECTION_PEER0_ORG2=true
   CORE_PEER_GOSSIP_ORGLEADER_PEER0_ORG3=false
   CORE_PEER_GOSSIP_USELEADERELECTION_PEER0_ORG3=true
   CORE_PEER_GOSSIP_ORGLEADER_PEER1_ORG1=false
   CORE_PEER_GOSSIP_USELEADERELECTION_PEER1_ORG1=true
   CORE_PEER_GOSSIP_ORGLEADER_PEER1_ORG2=false
   CORE_PEER_GOSSIP_USELEADERELECTION_PEER1_ORG2=true
   CORE_PEER_GOSSIP_ORGLEADER_PEER1_ORG3=false
   CORE_PEER_GOSSIP_USELEADERELECTION_PEER1_ORG3=true
   ORDERER_ABSOLUTEMAXBYTES=10 MB
   ORDERER_PREFERREDMAXBYTES=512 KB
   KAFKA_MESSAGE_MAX_BYTES=1000012 B
   KAFKA_REPLICA_FETCH_MAX_BYTES=1048576 B
   KAFKA_REPLICA_FETCH_RESPONSE_MAX_BYTES=10485760 B
   CORE_PEER_NETWORKID=net
   DOMAIN=<your_company_domain>
   FABRIC_CA_SERVER_TLS_ENABLED=false

6. chmod 777 *.sh
7. Generate the crypto-material. Input arguments to generate.sh are channelname and domain name : 

   ./generate.sh <channelname> <DOMAIN>

   For Example: ./generate.sh mychannel cogdevops.com

8. Start/Restart the Network :

   ./start.sh

9. Verify if all the docker containers are running

   docker ps
10. Create and Join channel in Anchor peer - peer0.org1:  

      Get into peer0.org1 container: docker exec -it peer0.org1.<DOMAIN> bash

      Create: peer channel create -o orderer0.<DOMAIN>:7050 -c mychannel -f /var/hyperledger/configs/channel.tx

    
    

      Join channel: peer channel join -o orderer0.<DOMAIN> -b mychannel.block
11. Fetch the block and join channel in other peers: 

    Get into peer0.org1 container: docker exec -it peer0.org1.<DOMAIN> bash

    
    

    Fetch block: peer channel fetch 0 mychannel.block --channelID mychannel --orderer orderer0.<DOMAIN>:7050

    Join: peer channel join -o orderer0.<DOMAIN> -b mychannel.block

12. Install,Instantiate the chaincode in Anchor peer - peer0. Get into respective peer containers and use the below install command to install chaincode in other peers.

      Get into peer0.org1 container: docker exec -it peer0.org1.<DOMAIN> bash

      Install: peer chaincode install -n insightsAuditing -p /chaincode/src/nodejs -l node -v 1.0

      Instantiate: peer chaincode instantiate -n insightsAuditing -v 1.0 -c '{"Args":["init"]}' -C mychannel

13. Get into ca container. Create user to connect from fabric sdk by using admin. Fabric sdk network connection requires the user's cert details to get connected to the fabric network.

    docker exec -it ca.org1.<DOMAIN> bash

    fabric-ca-client enroll -u http://Admin:<password>@localhost:7054

    fabric-ca-client register -u "http://localhost:7054" --id.name "newusername" --id.secret "password" --id.type "client" --id.affiliation "org1.department1"

    fabric-ca-client enroll -u "http://newusername:password@localhost:7054"

14. Test the Chaincode. Either insert record manually or let the data gets inserted via PlatformAuditEngine. Then, query as shown below. Modify ASSET-ID with your Asset ID value.
    

      Query: peer chaincode query -n insightsAuditing -c '{"Args":["GetAssetDetails","ASSET-ID"]}' -C mychannel

Make sure you've done all the Prerequisites. Raft Ordering Service introduced in 1.4.1 (Reference: https://hyperledger-fabric.readthedocs.io/en/release-1.4/whatsnew.html)

Ensure docker images are pulled as per raft supported version (1.4.1 , 1.4.2 as on 18.Jul.2019 - https://github.com/hyperledger/fabric/releases )

Network Architecture

• 5 Orderers
• 2 Organizations
• 4 peers, 2 for each organization
• 4 couchdb, one for each peer
• 2 certificate authority(CA), one for each organization
• 1 cli (Optional)

Setup the Network

1. Navigate to your home directory or any convenient directory and clone the Hyperledger_Raft branch from our repo:   

   git clone -b Hyperledger_Raft https://github.com/TheCognizantFoundry/Insights.git

2. Navigate into the raft-with-ca folder: cd Insights/raft-with-ca

3. Give permissions to all the executables and shell files which will easily bring up/down the network:
   chmod 777 *.sh
   chmod -R 755 bin

4. Generate the crypto-material. Input arguments to generate.sh are channelname and domain name : 

   ./generate.sh <channelname> <DOMAIN>

   For Example: ./generate.sh mychannel cogdevops.com

5. Edit the values(DOMAIN, CA_ORG*_KEYFILE etc.) inside the .env file. Refer the list below to know more about the variables of .env:

   • The tls variables must be set to true as Hyperledger-fabric Raft mandates enabling TLS for better security in network communication. Failing to do so will result in crashing of the orderers.

   • Some of the fields are pre-populated with default values. you may change the values as per requirement. The IMAGE_TAG must be >= 1.4.1 or latest to have raft setup.

   .env

   COMPOSE_PROJECT_NAME=<name_of_your_network>
   IMAGE_TAG=<docker_image_raft_supported_tag_1.4.1_or_1.4.2>
   DOMAIN=<yourCompany_domain_name>
   ORDERER_GENERAL_TLS_ENABLED=true
   CORE_PEER_TLS_ENABLED=true
   FABRIC_CA_SERVER_TLS_ENABLED=true
   ORDERER_TLS_CLIENTAUTHREQUIRED=true
   CA_ORG1_KEYFILE=<name of the keyfile residing inside crypto-config/peerOrganizations/org1.cogdevops.com/ca/>
   CA_ORG2_KEYFILE=<name of the keyfile residing inside crypto-config/peerOrganizations/org2.cogdevops.com/ca/>

   Hint

   Ensure docker images are pulled as per raft supported version >= 1.4.1

   To use raft fabric docker images: Sometimes fabric docker images are pulled with old network architecture(eg., solo) or already present in the system/VM for the image tag "latest", then remove the existing docker images using "docker rmi -f <imageid>" when respective containers are not running. Because, fabric-image with tag "latest" won't pull new image with actual latest tag due to existing reference. Below start.sh will pull the image as per the raft version >=1.4.1 defined in .env file.

6. Start the Network :

   ./start.sh <channelname> <DOMAIN>

   You must use the same  channelname and DOMAIN which you used in step 6.

   If you want to learn more about how the network is setup, then do not execute the start.sh. In stead, run the below commands manually from your terminal:

   Learn more about the steps performed inside start.sh Expand source

   #Replace $CHANNEL_NAME and $DOMAIN with your channelname and domain respectively.
   #setup the network
   docker-compose -f docker-compose-cli.yaml -f docker-compose-couch.yaml -f docker-compose-etcdraft2.yaml up -d
   sleep 15
   #create the channel
   docker exec -it peer0.org1.$DOMAIN peer channel create -o orderer.$DOMAIN:7050 -c $CHANNEL_NAME -f ./channel-artifacts/channel.tx --tls --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/$DOMAIN/orderers/orderer.$DOMAIN/msp/tlscacerts/tlsca.$DOMAIN-cert.pem
   
   #join org1 anchor peer peer0.org1
   docker exec -it peer0.org1.$DOMAIN peer channel join -b $CHANNEL_NAME.block
   #join org2 anchor peer0.org2
   docker exec -it peer0.org2.$DOMAIN peer channel fetch 0 $CHANNEL_NAME.block -c $CHANNEL_NAME -o orderer.$DOMAIN:7050 --tls --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/$DOMAIN/orderers/orderer.$DOMAIN/msp/tlscacerts/tlsca.$DOMAIN-cert.pem
   docker exec -it peer0.org2.$DOMAIN peer channel join -b $CHANNEL_NAME.block
   
   #join org1 & org2
   docker exec -it peer0.org1.$DOMAIN peer channel update -o orderer.$DOMAIN:7050 -c $CHANNEL_NAME -f ./channel-artifacts/Org1MSPanchors.tx --tls --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/$DOMAIN/orderers/orderer.$DOMAIN/msp/tlscacerts/tlsca.$DOMAIN-cert.pem
   docker exec -it peer0.org2.$DOMAIN peer channel update -o orderer.$DOMAIN:7050 -c $CHANNEL_NAME -f ./channel-artifacts/Org2MSPanchors.tx --tls --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/$DOMAIN/orderers/orderer.$DOMAIN/msp/tlscacerts/tlsca.$DOMAIN-cert.pem
   
   #join the other peers to the channel
   docker exec -it peer1.org1.$DOMAIN peer channel fetch 0 $CHANNEL_NAME.block -c $CHANNEL_NAME -o orderer.$DOMAIN:7050 --tls --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/$DOMAIN/orderers/orderer.$DOMAIN/msp/tlscacerts/tlsca.$DOMAIN-cert.pem
   docker exec -it peer1.org1.$DOMAIN peer channel join -b $CHANNEL_NAME.block
   
   docker exec -it peer1.org2.$DOMAIN peer channel fetch 0 $CHANNEL_NAME.block -c $CHANNEL_NAME -o orderer.$DOMAIN:7050 --tls --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/$DOMAIN/orderers/orderer.$DOMAIN/msp/tlscacerts/tlsca.$DOMAIN-cert.pem
   docker exec -it peer1.org2.$DOMAIN peer channel join -b $CHANNEL_NAME.block
   
   #install the chaincode into the anchor peers
   docker exec -it peer0.org1.$DOMAIN peer chaincode install -n insightsAudit -v 1.0 -l node -p /chaincode/src/nodejs/
   docker exec -it peer0.org2.$DOMAIN peer chaincode install -n insightsAudit -v 1.0 -l node -p /chaincode/src/nodejs/
   
   #install into the other peers
   docker exec -it peer1.org1.$DOMAIN peer chaincode install -n insightsAudit -v 1.0 -l node -p /chaincode/src/nodejs/
   docker exec -it peer1.org2.$DOMAIN peer chaincode install -n insightsAudit -v 1.0 -l node -p /chaincode/src/nodejs/
   
   #instantiate the chaincode inside one of the anchor (here we are doing for peer0.org1)
   docker exec -it peer0.org1.$DOMAIN peer chaincode instantiate -o orderer.$DOMAIN:7050 --tls --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/$DOMAIN/orderers/orderer.$DOMAIN/msp/tlscacerts/tlsca.$DOMAIN-cert.pem -C $CHANNEL_NAME -n insightsAudit -l node -v 1.0 -c '{"Args":["Init"]}'

7. Verify if all the docker containers are running:

   docker ps -a

   You will notice some extra containers running other than the ones mentioned in the network architecture with names like this: dev-peer0.org1.cogdevops.com-insightsAudit-1.0. It is an expected behaviour for the fabric-network. These containers will get spawned whenever chaincode is instantiated in a peer. Since the start.sh script will instantiate the chaincode inside peer0 by default, therefore this container will get spawned.

   At this point your raft setup is complete. Steps mentioned hereafter are for registration and enrollment of a user to be used with SDK.

8. Login into the CA container: docker exec -it ca.org1.<DOMAIN> bash
9. Run the following inside the container:

• Enroll the admin: fabric-ca-client enroll -u https://Admin:adminpw@localhost:7054 --tls.certfiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.<DOMAIN>/ca/ca.org1.<DOMAIN>-cert.pem
• Now register a new user: fabric-ca-client register -u https://localhost:7054 --id.name "newusername" --id.secret "password" --id.type "client" --id.affiliation "org1.department1" --tls.certfiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.<DOMAIN>/ca/ca.org1.<DOMAIN>-cert.pem
• Verify the registration by listing the available users: fabric-ca-client identity list -u https://localhost:7054 --tls.certfiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.<DOMAIN>/ca/ca.org1.<DOMAIN>-cert.pem

You should see the new user inside this list if registration is successful.

     12. Test the Chaincode. Either insert record manually or let the data gets inserted via PlatformAuditEngine. Then run the below query inside any of the peers.             Modify assetID with your Asset ID value and channelname should be the same one used in step 8.

        Query: peer chaincode query -n insightsAuditing -c '{"Args":["GetAssetDetails","<assetID>"]}' -C <channelname>