4. 将fabric链码部署到测试网络的记录

系列文章目录

1. Fabric2.2在Linux上的部署记录
2. Fabric2.2测试网络(test-network)的使用记录
3. 用go编写简单的fabric链码
4. 将fabric链码部署到测试网络的记录
5. 利用fabric-gateway-java连接并调用fabric链码

---

前言

在上一篇文章中，利用go编写了简单的fabric链码，本文将编写完成的链码部署到测试网络(test-network)的过程做一个记录总结。

一、链码部署的流程

1. 打包链码
2. 安装链码包
3. 批准链码定义
4. 将链码定义提交至通道

二、具体步骤

1.启动测试网络

cd fabric-samples/test-network
./network.sh down
./network.sh up createChannel

2.打包链码

• 设置环境变量

export PATH=${PWD}/../bin:$PATH
export FABRIC_CFG_PATH=$PWD/../config/

• 添加链码名字的环境变量

export CHAINCODE_NAME=<chaincode-name>

这里的<chaincode-name>替换成自定义的链码名字，下同。利用环境变量方便后续的部署操作。

• 打包链码

peer lifecycle chaincode package $CHAINCODE_NAME.tar.gz \
--path ../asset-transfer-basic/<chaincode-folder>/ \ #注意替换链码文件路径
--lang golang \
--label <chaincode-name>_1.0 #注意替换<chaincode-name>内容

3.安装链码

• 以org1身份运行

export CORE_PEER_TLS_ENABLED=true
export CORE_PEER_LOCALMSPID="Org1MSP"
export CORE_PEER_TLS_ROOTCERT_FILE=${PWD}/organizations/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt
export CORE_PEER_MSPCONFIGPATH=${PWD}/organizations/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp
export CORE_PEER_ADDRESS=localhost:7051

• 在org1安装链码

peer lifecycle chaincode install $CHAINCODE_NAME.tar.gz

• 以org2身份运行

export CORE_PEER_LOCALMSPID="Org2MSP"
export CORE_PEER_TLS_ROOTCERT_FILE=${PWD}/organizations/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt
export CORE_PEER_TLS_ROOTCERT_FILE=${PWD}/organizations/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt
export CORE_PEER_MSPCONFIGPATH=${PWD}/organizations/peerOrganizations/org2.example.com/users/Admin@org2.example.com/msp
export CORE_PEER_ADDRESS=localhost:9051

• 在org2安装链码

peer lifecycle chaincode install $CHAINCODE_NAME.tar.gz

• 查询链码包ID

peer lifecycle chaincode queryinstalled

• 添加链码包ID的环境变量

export CC_PACKAGE_ID=<Package ID> #注意替换这里的链码包ID

4.批准链码定义

• org2同意该链码定义

peer lifecycle chaincode approveformyorg \
-o localhost:7050 \
--ordererTLSHostnameOverride orderer.example.com \
--channelID mychannel \
--name $CHAINCODE_NAME \
--version 1.0 \
--package-id $CC_PACKAGE_ID \
--sequence 1 \
--tls \
--cafile ${PWD}/organizations/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem

注意，此时是以org2身份运行。根据背书策略，org1和org2均要同意此链码定义才能提交，于是下一步即为org1同意此链码定义。

• 切换到org1

export CORE_PEER_LOCALMSPID="Org1MSP"
export CORE_PEER_MSPCONFIGPATH=${PWD}/organizations/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp
export CORE_PEER_TLS_ROOTCERT_FILE=${PWD}/organizations/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt
export CORE_PEER_ADDRESS=localhost:7051

• org1同意该链码定义

peer lifecycle chaincode approveformyorg \
-o localhost:7050 \
--ordererTLSHostnameOverride orderer.example.com \
--channelID mychannel \
--name $CHAINCODE_NAME \
--version 1.0 \
--package-id $CC_PACKAGE_ID \
--sequence 1 \
--tls \
--cafile ${PWD}/organizations/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem

• 检查同意情况

peer lifecycle chaincode checkcommitreadiness \
--channelID mychannel \
--name $CHAINCODE_NAME \
--version 1.0 \
--sequence 1 \
--tls \
--cafile ${PWD}/organizations/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem \
--output json

5.提交链码

peer lifecycle chaincode commit \
-o localhost:7050 \
--ordererTLSHostnameOverride orderer.example.com \
--channelID mychannel \
--name $CHAINCODE_NAME \
--version 1.0 \
--sequence 1 \
--tls \
--cafile ${PWD}/organizations/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem \
--peerAddresses localhost:7051 \
--tlsRootCertFiles ${PWD}/organizations/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt \
--peerAddresses localhost:9051 \
--tlsRootCertFiles ${PWD}/organizations/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt

注意，这里是以org1身份提交的链码，亦可以用org2进行提交，只需一方提交一次即可。

• 确认是否提交

peer lifecycle chaincode querycommitted \
--channelID mychannel \
--name $CHAINCODE_NAME \
--cafile ${PWD}/organizations/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem

6.调用链码

• 初始化资产

peer chaincode invoke \
-o localhost:7050 \
--ordererTLSHostnameOverride orderer.example.com \
--tls \
--cafile ${PWD}/organizations/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem \
-C mychannel \
-n $CHAINCODE_NAME \
--peerAddresses localhost:7051 \
--tlsRootCertFiles ${PWD}/organizations/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt \
--peerAddresses localhost:9051 \
--tlsRootCertFiles ${PWD}/organizations/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt \
-c '{"function":"initLedger","Args":[]}'

• 查询所有资产

peer chaincode query \
-C mychannel \
-n $CHAINCODE_NAME \
-c '{"Args":["getAllAssets"]}'

到这里，自定义的链码已经部署到测试网络上，在测试完毕后可关闭网络。

./network.sh down

总结

本文记录下了自定义的链码部署到fabric测试网络的过程，过程并不复杂，若想方便进行部署，可以将以上命令写成脚本。接下来会尝试利用java的SDK对部署好的链码进行调用。以上内容如有不正，请多多指教。