Page Comparison

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.

   Code Block
   language applescript theme Emacs title .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) :

          Code Block
          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.

   Code Block
   language bash theme Emacs title .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