Update docs
qiang0723
parent
604e02174b
commit
3342e619a4
|
|
@ -120,240 +120,35 @@ UTC [main] main -> INFO 008 Exiting.....
|
|||
|_____| |_| \_| |____/
|
||||
```
|
||||
|
||||
At last, you can fetch blocks using following command:
|
||||
So far, we have quickly started a fabric network successfully.
|
||||
|
||||
```bash
|
||||
$ NUM= the block's num you want to fetch
|
||||
$ peer channel fetch $NUM -o orderer.example.com:7050 -c businesschannel
|
||||
```
|
||||
In this example, we `install` 4 times, and `invoke` 2 times, so we have 6 blocks in total, and we put it into `/e2e_cli/channel-artifacts`.
|
||||
you can also use following command to fetch blocks:
|
||||
## Expand
|
||||
|
||||
```bash
|
||||
$ peer channel fetch oldest -o orderer.example.com:7050 -c businesschannel
|
||||
$ peer channel fetch newest -o orderer.example.com:7050 -c businesschannel
|
||||
```
|
||||
### [Explain the steps](./docs/docker-compose-1peer-usage.md)
|
||||
|
||||
## Explain the steps
|
||||
Explain in detail how a 1-peer network start and test
|
||||
|
||||
This section will show you how to operate the chaincode in detail.
|
||||
first start fabric network with `docker-compose-1peer.yaml`, and we will obtain the basic environmet that can be operated.
|
||||
|
||||
```bash
|
||||
$ docker-compose -f docker-compose-1peer.yaml up
|
||||
```
|
||||
### [Fetch blocks](./docs/peer-command-usage.md)
|
||||
|
||||
There will be 4 containers running successfully.
|
||||
Fetch blocks using peer channel fetch
|
||||
|
||||
```bash
|
||||
$ docker ps
|
||||
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
|
||||
6688f290a9b9 hyperledger/fabric-peer "bash -c 'while tr..." About a minute ago Up About a minute 7050-7059/tcp fabric-cli
|
||||
6ddbbd972ac3 hyperledger/fabric-peer "peer node start -..." About a minute ago Up About a minute 7050/tcp, 0.0.0.0:7051->7051/tcp, 7052/tcp, 7054-7059/tcp, 0.0.0.0:7053->7053/tcp peer0.org1.example.com
|
||||
4afc759e0dc9 hyperledger/fabric-orderer "orderer" About a minute ago Up About a minute 0.0.0.0:7050->7050/tcp orderer.example.com
|
||||
bea1154c7162 hyperledger/fabric-ca "fabric-ca-server ..." About a minute ago Up About a minute 7054/tcp, 0.0.0.0:7054->7054/tcp fabric-ca
|
||||
```
|
||||
|
||||
### Manually testing
|
||||
### [Events](./docs/events.md)
|
||||
|
||||
#### Create artifacts
|
||||
Get events with block-listener
|
||||
|
||||
**You can skip this step**, as we already put the needed artifacts `orderer.genesis.block` and `channel.tx` under `e2e_cli/channel-artifacts/`.
|
||||
|
||||
Detailed steps in [GenerateArtifacts](./artifacts_generation/artifacts_generation.md) explains the creation of `orderer.genesis.block` (needed by orderering service) and `channel.tx` (needed by cli to create new channel) and crypto related configuration files.
|
||||
### [Tool usage](./artifacts_generation/artifacts_generation.md)
|
||||
|
||||
#### Create new channel
|
||||
Will explain the usage of `cryptogen` and `configtxgen`
|
||||
|
||||
Create a new channel named `mychannel` with the existing `channel.tx` file.
|
||||
|
||||
```bash
|
||||
$ docker exec -it fabric-cli bash
|
||||
```
|
||||
Into the container and execute following commands:
|
||||
### [WIP] [Some verification tests](./docs/Verification-test.md)
|
||||
|
||||
```bash
|
||||
$ CHANNEL_NAME="mychannel"
|
||||
$ peer channel create -o orderer.example.com:7050 -c ${CHANNEL_NAME} -f ./channel-artifacts/channel.tx
|
||||
```
|
||||
The cmd will return lots of info, which is the content of the configuration block.
|
||||
|
||||
And a block with the same name of the channel will be created locally.
|
||||
### [WIP] [Use couchDB](./docs/couchdb-usage.md)
|
||||
|
||||
```bash
|
||||
$ ls mychannel.block
|
||||
mychannel.block
|
||||
```
|
||||
|
||||
Check the log output of `orderer.example.com`, should find some message like
|
||||
|
||||
```bash
|
||||
orderer.example.com | UTC [orderer/multichain] newChain -> INFO 004 Created and starting new chain newchannel
|
||||
```
|
||||
|
||||
#### Join the channel
|
||||
|
||||
Use the following command to join `peer0.org1.example.com` the channel
|
||||
|
||||
```bash
|
||||
$ peer channel join -b ${CHANNEL_NAME}.block
|
||||
|
||||
Peer joined the channel!
|
||||
```
|
||||
|
||||
Will receive the `Peer joined the channel!` response if succeed.
|
||||
|
||||
Then use the following command, we will find the channels that peers joined.
|
||||
|
||||
```bash
|
||||
$ peer channel list
|
||||
Channels peers has joined to:
|
||||
mychannel
|
||||
2017-04-11 03:44:40.313 UTC [main] main -> INFO 001 Exiting.....
|
||||
```
|
||||
|
||||
#### Update anchor peers
|
||||
|
||||
The `configtx.yaml` file contains the definitions for our sample network and presents the topology of the network components - three members (OrdererOrg, Org1 & Org2), But in this MVE, we just use OrdererOrg and Org1, org1 has only peer(pee0.org1), and chose it as anchor peers for Org1.
|
||||
|
||||
```bash
|
||||
$ peer channel create -o orderer.example.com:7050 -c ${CHANNEL_NAME} -f ./channel-artifacts/Org1MSPanchors.tx
|
||||
```
|
||||
|
||||
#### Install&Instantiate
|
||||
|
||||
First `install` a chaincode named `mycc` to `peer0`.
|
||||
|
||||
```bash
|
||||
$ peer chaincode install -n mycc -v 1.0 -p github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example02
|
||||
```
|
||||
|
||||
This will take a while, and the result may look like following.
|
||||
|
||||
```bash
|
||||
UTC [golang-platform] writeGopathSrc -> INFO 004 rootDirectory = /go/src
|
||||
UTC [container] WriteFolderToTarPackage -> INFO 005 rootDirectory = /go/src
|
||||
UTC [main] main -> INFO 006 Exiting.....
|
||||
```
|
||||
|
||||
Then `instantiate` the chaincode mycc on channel `mychannel`, with initial args and the endorsement policy.
|
||||
|
||||
```bash
|
||||
$ peer chaincode instantiate -o orderer.example.com:7050 -C ${CHANNEL_NAME} -n mycc -v 1.0 -c '{"Args":["init","a","100","b","200"]}' -P "OR ('Org1MSP.member')"
|
||||
```
|
||||
|
||||
This will take a while, and the result may look like following:
|
||||
|
||||
```bash
|
||||
UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 004 Using default escc
|
||||
UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 005 Using default vscc
|
||||
UTC [main] main -> INFO 006 Exiting.....
|
||||
```
|
||||
|
||||
Now in the system, there will be a new `dev-peer0.org1.example.com-mycc-1.0` image and a `dev-peer0.org1.example.com-mycc-1.0` chaincode container.
|
||||
|
||||
```bash
|
||||
crluser@baas-test2:~$ docker ps
|
||||
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
|
||||
7aa088c76597 dev-peer0.org1.example.com-mycc-1.0 "chaincode -peer.a..." 10 seconds ago Up 9 seconds dev-peer0.org1.example.com-mycc-1.0
|
||||
eb1d9c73b26b hyperledger/fabric-peer "bash -c 'while tr..." About a minute ago Up About a minute 7050-7059/tcp fabric-cli
|
||||
2d6fd4f61e2b hyperledger/fabric-peer "peer node start -..." About a minute ago Up About a minute 7050/tcp, 0.0.0.0:7051->7051/tcp, 7052/tcp, 7054-7059/tcp, 0.0.0.0:7053->7053/tcp peer0.org1.example.com
|
||||
832dcc64cc1b hyperledger/fabric-orderer "orderer" About a minute ago Up About a minute 0.0.0.0:7050->7050/tcp orderer.example.com
|
||||
c87095528f76 hyperledger/fabric-ca "fabric-ca-server ..." About a minute ago Up About a minute 7054/tcp, 0.0.0.0:7054->7054/tcp fabric-ca
|
||||
```
|
||||
|
||||
#### Query
|
||||
|
||||
Query the existing value of `a` and `b`.
|
||||
|
||||
```bash
|
||||
$ peer chaincode query -C ${CHANNEL_NAME} -n mycc -c '{"Args":["query","a"]}'
|
||||
```
|
||||
|
||||
The result may look like following, with a payload value of `100`.
|
||||
```bash
|
||||
Query Result: 100
|
||||
[main] main -> INFO 001 Exiting.....
|
||||
```
|
||||
|
||||
```bash
|
||||
$ peer chaincode query -C ${CHANNEL_NAME} -n mycc -c '{"Args":["query","a"]}'
|
||||
```
|
||||
|
||||
The result may look like following, with a payload value of `200`.
|
||||
|
||||
```bash
|
||||
Query Result: 200
|
||||
[main] main -> INFO 001 Exiting.....
|
||||
```
|
||||
|
||||
|
||||
#### Invoke
|
||||
|
||||
Inside the container, invoke a transaction to transfer `10` from `a` to `b`.
|
||||
|
||||
```bash
|
||||
$ peer chaincode invoke -o orderer.example.com:7050 -C ${CHANNEL_NAME} -n mycc -c '{"Args":["invoke","a","b","10"]}'
|
||||
```
|
||||
|
||||
The result may look like following:
|
||||
|
||||
```bash
|
||||
UTC [chaincodeCmd] chaincodeInvokeOrQuery -> INFO 001 Invoke result: version:1 response:<status:200 message:"OK" > payload:"\n qm\251\207\312\277\256\261b\317:\300\000\014\203`\005\304\254\304,$a\360\327\010\342\342/y]\323\022X\nQ\022\031\n\004lccc\022\021\n\017\n\007test_cc\022\004\010\001\020\001\0224\n\007test_cc\022)\n\t\n\001a\022\004\010\001\020\001\n\t\n\001b\022\004\010\001\020\001\032\007\n\001a\032\00290\032\010\n\001b\032\003210\032\003\010\310\001" endorsement:<endorser:"\n\007Org0MSP\022\210\004-----BEGIN -----\nMIIBYzCCAQmgAwIBAwICA+gwCgYIKoZIzj0EAwIwEzERMA8GA1UEAwwIcGVlck9y\nZzAwHhcNMTcwMjIwMTkwNjExWhcNMTgwMjIwMTkwNjExWjAQMQ4wDAYDVQQDDAVw\nZWVyMDBZMBMGByqGSM49AgEGCCqGSM49AwEHA0IABEF6dfqjqfbIgZuOR+dgoJMl\n/FaUlGI70A/ixmVUY83Yp4YtV3FDBSOPiO5O+s8pHnpbwB1LqhrxAx1Plr0M/UWj\nUDBOMAwGA1UdEwEB/wQCMAAwHQYDVR0OBBYEFBY2bc84vLEwkX1fSAER2p48jJXw\nMB8GA1UdIwQYMBaAFFQzuQR1RZP/Qn/BNDtGSa8n4eN/MAoGCCqGSM49BAMCA0gA\nMEUCIQDeDZ71L+OTYcbbqiDNRf0L8OExO59mH1O3xpdwMAM0MgIgXySG4sv9yV31\nWcWRFfRFyu7o3T72kqiLZ1nkDuJ8jWI=\n-----END -----\n" signature:"0E\002!\000\220M'\245\230do\310>\277\251j\021$\250\237H\353\377\331:\230\362n\216\224~\033\240\006\367%\002 \014\240|h\346\250\356\372\353\301;#\372\027\276!\252F\334/\221\210\254\215\363\235\341v\217\236\274<" >
|
||||
2017-04-06 09:47:15.993 UTC [main] main -> INFO 002 Exiting.....
|
||||
```
|
||||
|
||||
#### Query
|
||||
|
||||
And then query the value of `a` and `b`.
|
||||
|
||||
|
||||
```bash
|
||||
$ peer chaincode query -C ${CHANNEL_NAME} -n mycc -c '{"Args":["query","a"]}'
|
||||
```
|
||||
|
||||
```bash
|
||||
Query Result: 90
|
||||
[main] main -> INFO 001 Exiting.....
|
||||
```
|
||||
The value of `a` should be `90`.
|
||||
|
||||
|
||||
```bash
|
||||
$ peer chaincode query -C ${CHANNEL_NAME} -n mycc -c '{"Args":["query","b"]}'
|
||||
```
|
||||
|
||||
The value of `b` should be `210`
|
||||
|
||||
```bash
|
||||
Query Result: 210
|
||||
[main] main -> INFO 001 Exiting.....
|
||||
```
|
||||
|
||||
Finally, the output of the chaincode containers may look like following.
|
||||
|
||||
```bash
|
||||
$ docker logs -f dev-peer0.org1.example.com-mycc-1.0
|
||||
ex02 Init
|
||||
Aval = 100, Bval = 200
|
||||
ex02 Invoke
|
||||
Query Response:{"Name":"a","Amount":"100"}
|
||||
ex02 Invoke
|
||||
Aval = 90, Bval = 210
|
||||
ex02 Invoke
|
||||
Query Response:{"Name":"b","Amount":"210"}
|
||||
ex02 Invoke
|
||||
Query Response:{"Name":"a","Amount":"90"}
|
||||
|
||||
```
|
||||
|
||||
### (optional) All-in-one testing operation
|
||||
|
||||
Run this script will check whether the MVE bootstrap success.
|
||||
|
||||
```bash
|
||||
$ docker exec -it fabric-cli bash
|
||||
$ bash ./peer/scripts/new-channel-auto-test.sh
|
||||
```
|
||||
|
||||
## Acknowledgement
|
||||
* [Hyperledger Fabric](https://github.com/hyperledger/fabric/) project.
|
||||
|
|
|
|||
|
|
@ -0,0 +1,219 @@
|
|||
### Explain 1-peer usage step by step
|
||||
|
||||
This section will show you how to operate the chaincode in detail.
|
||||
first start fabric network with `docker-compose-1peer.yaml`, and we will obtain the basic environmet that can be operated.
|
||||
|
||||
```bash
|
||||
$ docker-compose -f docker-compose-1peer.yaml up
|
||||
```
|
||||
|
||||
There will be 4 containers running successfully.
|
||||
|
||||
```bash
|
||||
$ docker ps
|
||||
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
|
||||
6688f290a9b9 hyperledger/fabric-peer "bash -c 'while tr..." About a minute ago Up About a minute 7050-7059/tcp fabric-cli
|
||||
6ddbbd972ac3 hyperledger/fabric-peer "peer node start -..." About a minute ago Up About a minute 7050/tcp, 0.0.0.0:7051->7051/tcp, 7052/tcp, 7054-7059/tcp, 0.0.0.0:7053->7053/tcp peer0.org1.example.com
|
||||
4afc759e0dc9 hyperledger/fabric-orderer "orderer" About a minute ago Up About a minute 0.0.0.0:7050->7050/tcp orderer.example.com
|
||||
bea1154c7162 hyperledger/fabric-ca "fabric-ca-server ..." About a minute ago Up About a minute 7054/tcp, 0.0.0.0:7054->7054/tcp fabric-ca
|
||||
```
|
||||
|
||||
|
||||
#### Create artifacts
|
||||
|
||||
**You can skip this step**, as we already put the needed artifacts `orderer.genesis.block` and `channel.tx` under `e2e_cli/channel-artifacts/`.
|
||||
|
||||
Detailed steps in [GenerateArtifacts](../artifacts_generation/artifacts_generation.md) explains the creation of `orderer.genesis.block` (needed by orderering service) and `channel.tx` (needed by cli to create new channel) and crypto related configuration files.
|
||||
|
||||
#### Create new channel
|
||||
|
||||
Create a new channel named `mychannel` with the existing `channel.tx` file.
|
||||
|
||||
```bash
|
||||
$ docker exec -it fabric-cli bash
|
||||
```
|
||||
Into the container and execute following commands:
|
||||
|
||||
```bash
|
||||
$ CHANNEL_NAME="businesschannel"
|
||||
$ peer channel create -o orderer.example.com:7050 -c ${CHANNEL_NAME} -f ./channel-artifacts/channel.tx
|
||||
```
|
||||
The cmd will return lots of info, which is the content of the configuration block.
|
||||
|
||||
And a block with the same name of the channel will be created locally.
|
||||
|
||||
```bash
|
||||
$ ls businesschannel.block
|
||||
businesschannel.block
|
||||
```
|
||||
|
||||
Check the log output of `orderer.example.com`, should find some message like
|
||||
|
||||
```bash
|
||||
orderer.example.com | UTC [orderer/multichain] newChain -> INFO 004 Created and starting new chain newchannel
|
||||
```
|
||||
|
||||
#### Join the channel
|
||||
|
||||
Use the following command to join `peer0.org1.example.com` the channel
|
||||
|
||||
```bash
|
||||
$ peer channel join -b ${CHANNEL_NAME}.block
|
||||
|
||||
Peer joined the channel!
|
||||
```
|
||||
|
||||
Will receive the `Peer joined the channel!` response if succeed.
|
||||
|
||||
Then use the following command, we will find the channels that peers joined.
|
||||
|
||||
```bash
|
||||
$ peer channel list
|
||||
Channels peers has joined to:
|
||||
mychannel
|
||||
2017-04-11 03:44:40.313 UTC [main] main -> INFO 001 Exiting.....
|
||||
```
|
||||
|
||||
#### Update anchor peers
|
||||
|
||||
The `configtx.yaml` file contains the definitions for our sample network and presents the topology of the network components - three members (OrdererOrg, Org1 & Org2), But in this MVE, we just use OrdererOrg and Org1, org1 has only peer(pee0.org1), and chose it as anchor peers for Org1.
|
||||
|
||||
```bash
|
||||
$ peer channel create -o orderer.example.com:7050 -c ${CHANNEL_NAME} -f ./channel-artifacts/Org1MSPanchors.tx
|
||||
```
|
||||
|
||||
#### Install&Instantiate
|
||||
|
||||
First `install` a chaincode named `mycc` to `peer0`.
|
||||
|
||||
```bash
|
||||
$ peer chaincode install -n mycc -v 1.0 -p github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example02
|
||||
```
|
||||
|
||||
This will take a while, and the result may look like following.
|
||||
|
||||
```bash
|
||||
UTC [golang-platform] writeGopathSrc -> INFO 004 rootDirectory = /go/src
|
||||
UTC [container] WriteFolderToTarPackage -> INFO 005 rootDirectory = /go/src
|
||||
UTC [main] main -> INFO 006 Exiting.....
|
||||
```
|
||||
|
||||
Then `instantiate` the chaincode mycc on channel `mychannel`, with initial args and the endorsement policy.
|
||||
|
||||
```bash
|
||||
$ peer chaincode instantiate -o orderer.example.com:7050 -C ${CHANNEL_NAME} -n mycc -v 1.0 -c '{"Args":["init","a","100","b","200"]}' -P "OR ('Org1MSP.member')"
|
||||
```
|
||||
|
||||
This will take a while, and the result may look like following:
|
||||
|
||||
```bash
|
||||
UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 004 Using default escc
|
||||
UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 005 Using default vscc
|
||||
UTC [main] main -> INFO 006 Exiting.....
|
||||
```
|
||||
|
||||
Now in the system, there will be a new `dev-peer0.org1.example.com-mycc-1.0` image and a `dev-peer0.org1.example.com-mycc-1.0` chaincode container.
|
||||
|
||||
```bash
|
||||
crluser@baas-test2:~$ docker ps
|
||||
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
|
||||
7aa088c76597 dev-peer0.org1.example.com-mycc-1.0 "chaincode -peer.a..." 10 seconds ago Up 9 seconds dev-peer0.org1.example.com-mycc-1.0
|
||||
eb1d9c73b26b hyperledger/fabric-peer "bash -c 'while tr..." About a minute ago Up About a minute 7050-7059/tcp fabric-cli
|
||||
2d6fd4f61e2b hyperledger/fabric-peer "peer node start -..." About a minute ago Up About a minute 7050/tcp, 0.0.0.0:7051->7051/tcp, 7052/tcp, 7054-7059/tcp, 0.0.0.0:7053->7053/tcp peer0.org1.example.com
|
||||
832dcc64cc1b hyperledger/fabric-orderer "orderer" About a minute ago Up About a minute 0.0.0.0:7050->7050/tcp orderer.example.com
|
||||
c87095528f76 hyperledger/fabric-ca "fabric-ca-server ..." About a minute ago Up About a minute 7054/tcp, 0.0.0.0:7054->7054/tcp fabric-ca
|
||||
```
|
||||
|
||||
#### Query
|
||||
|
||||
Query the existing value of `a` and `b`.
|
||||
|
||||
```bash
|
||||
$ peer chaincode query -C ${CHANNEL_NAME} -n mycc -c '{"Args":["query","a"]}'
|
||||
```
|
||||
|
||||
The result may look like following, with a payload value of `100`.
|
||||
```bash
|
||||
Query Result: 100
|
||||
[main] main -> INFO 001 Exiting.....
|
||||
```
|
||||
|
||||
```bash
|
||||
$ peer chaincode query -C ${CHANNEL_NAME} -n mycc -c '{"Args":["query","a"]}'
|
||||
```
|
||||
|
||||
The result may look like following, with a payload value of `200`.
|
||||
|
||||
```bash
|
||||
Query Result: 200
|
||||
[main] main -> INFO 001 Exiting.....
|
||||
```
|
||||
|
||||
|
||||
#### Invoke
|
||||
|
||||
Inside the container, invoke a transaction to transfer `10` from `a` to `b`.
|
||||
|
||||
```bash
|
||||
$ peer chaincode invoke -o orderer.example.com:7050 -C ${CHANNEL_NAME} -n mycc -c '{"Args":["invoke","a","b","10"]}'
|
||||
```
|
||||
|
||||
The result may look like following:
|
||||
|
||||
```bash
|
||||
UTC [chaincodeCmd] chaincodeInvokeOrQuery -> INFO 001 Invoke result: version:1 response:<status:200 message:"OK" > payload:"\n qm\251\207\312\277\256\261b\317:\300\000\014\203`\005\304\254\304,$a\360\327\010\342\342/y]\323\022X\nQ\022\031\n\004lccc\022\021\n\017\n\007test_cc\022\004\010\001\020\001\0224\n\007test_cc\022)\n\t\n\001a\022\004\010\001\020\001\n\t\n\001b\022\004\010\001\020\001\032\007\n\001a\032\00290\032\010\n\001b\032\003210\032\003\010\310\001" endorsement:<endorser:"\n\007Org0MSP\022\210\004-----BEGIN -----\nMIIBYzCCAQmgAwIBAwICA+gwCgYIKoZIzj0EAwIwEzERMA8GA1UEAwwIcGVlck9y\nZzAwHhcNMTcwMjIwMTkwNjExWhcNMTgwMjIwMTkwNjExWjAQMQ4wDAYDVQQDDAVw\nZWVyMDBZMBMGByqGSM49AgEGCCqGSM49AwEHA0IABEF6dfqjqfbIgZuOR+dgoJMl\n/FaUlGI70A/ixmVUY83Yp4YtV3FDBSOPiO5O+s8pHnpbwB1LqhrxAx1Plr0M/UWj\nUDBOMAwGA1UdEwEB/wQCMAAwHQYDVR0OBBYEFBY2bc84vLEwkX1fSAER2p48jJXw\nMB8GA1UdIwQYMBaAFFQzuQR1RZP/Qn/BNDtGSa8n4eN/MAoGCCqGSM49BAMCA0gA\nMEUCIQDeDZ71L+OTYcbbqiDNRf0L8OExO59mH1O3xpdwMAM0MgIgXySG4sv9yV31\nWcWRFfRFyu7o3T72kqiLZ1nkDuJ8jWI=\n-----END -----\n" signature:"0E\002!\000\220M'\245\230do\310>\277\251j\021$\250\237H\353\377\331:\230\362n\216\224~\033\240\006\367%\002 \014\240|h\346\250\356\372\353\301;#\372\027\276!\252F\334/\221\210\254\215\363\235\341v\217\236\274<" >
|
||||
2017-04-06 09:47:15.993 UTC [main] main -> INFO 002 Exiting.....
|
||||
```
|
||||
|
||||
#### Query
|
||||
|
||||
And then query the value of `a` and `b`.
|
||||
|
||||
|
||||
```bash
|
||||
$ peer chaincode query -C ${CHANNEL_NAME} -n mycc -c '{"Args":["query","a"]}'
|
||||
```
|
||||
|
||||
```bash
|
||||
Query Result: 90
|
||||
[main] main -> INFO 001 Exiting.....
|
||||
```
|
||||
The value of `a` should be `90`.
|
||||
|
||||
|
||||
```bash
|
||||
$ peer chaincode query -C ${CHANNEL_NAME} -n mycc -c '{"Args":["query","b"]}'
|
||||
```
|
||||
|
||||
The value of `b` should be `210`
|
||||
|
||||
```bash
|
||||
Query Result: 210
|
||||
[main] main -> INFO 001 Exiting.....
|
||||
```
|
||||
|
||||
Finally, the output of the chaincode containers may look like following.
|
||||
|
||||
```bash
|
||||
$ docker logs -f dev-peer0.org1.example.com-mycc-1.0
|
||||
ex02 Init
|
||||
Aval = 100, Bval = 200
|
||||
ex02 Invoke
|
||||
Query Response:{"Name":"a","Amount":"100"}
|
||||
ex02 Invoke
|
||||
Aval = 90, Bval = 210
|
||||
ex02 Invoke
|
||||
Query Response:{"Name":"b","Amount":"210"}
|
||||
ex02 Invoke
|
||||
Query Response:{"Name":"a","Amount":"90"}
|
||||
|
||||
```
|
||||
|
||||
#### (optional) All-in-one testing operation
|
||||
|
||||
Run this script will check whether the MVE bootstrap success.
|
||||
|
||||
```bash
|
||||
$ docker exec -it fabric-cli bash
|
||||
$ bash ./scripts/test_1peer.sh
|
||||
```
|
||||
|
|
@ -0,0 +1,33 @@
|
|||
## Events
|
||||
Events didn't support TLS, so make sure TLS has been disabled by setting *_TLS_ENABLED=false in peer-base.yaml and orderer-base.yaml
|
||||
Next, start the network with following command:
|
||||
```bash
|
||||
$ bash scripts/start_fabric.sh docker-compose-2orgs-4peers-event.yaml
|
||||
```
|
||||
|
||||
when the network starts successfully, we started a block-listener in container `fabric-event-listener`.
|
||||
so observe the output of the service fabric-event-listener.
|
||||
|
||||
Listening logs at a new terminal,
|
||||
|
||||
```bash
|
||||
$ docker logs -f fabric-event-listener
|
||||
```
|
||||
|
||||
So when we do chaincode operations in container `fabric-cli`,
|
||||
|
||||
```bash
|
||||
$ docker exec -it fabric-cli bash
|
||||
$ bash ./scripts/initialize.sh
|
||||
```
|
||||
|
||||
then we will get some events at listening terminal looks like following:
|
||||
|
||||
```bash
|
||||
Received block
|
||||
--------------
|
||||
Received transaction from channel businesschannel:
|
||||
[header:<channel_header:"\010\003\032\014\010\305\326\216\312\005\020\371\326\244\314\003\"\017businesschannel*@
|
||||
633caf1cd9796d49a58898c873bd10055867113f4eeb051a057acbce7df0ed59:\010\022\006\022\004lscc"
|
||||
signature_header:"\n\250\006\n\007Org2MSP\022\234\006-----BEGIN...
|
||||
```
|
||||
|
|
@ -0,0 +1,37 @@
|
|||
## peer channel fetch
|
||||
|
||||
### Under no-tls
|
||||
|
||||
When you set *TLS_ENABLED=false, then you can fetch blocks using following command:
|
||||
|
||||
```bash
|
||||
$ NUM= the block's num you want to fetch
|
||||
$ peer channel fetch $NUM -o orderer.example.com:7050 -c businesschannel
|
||||
```
|
||||
or you can use self-defined file, such as:
|
||||
|
||||
```bash
|
||||
$ peer channel fetch $NUM self-define-file.block -o orderer.example.com:7050 -c businesschannel
|
||||
```
|
||||
|
||||
For example, we `install` 4 times, and `invoke` 2 times, so we have 6 blocks in total, and we put it into `/e2e_cli/channel-artifacts`.
|
||||
you can also use following command to fetch blocks:
|
||||
|
||||
```bash
|
||||
$ peer channel fetch oldest -o orderer.example.com:7050 -c businesschannel
|
||||
$ peer channel fetch newest -o orderer.example.com:7050 -c businesschannel
|
||||
```
|
||||
|
||||
### Under tls
|
||||
|
||||
When you set *TLS_ENABLED=true, then you can fetch blocks using following command:
|
||||
|
||||
```bash
|
||||
$ ORDERER_CA=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/cacerts/ca.example.com-cert.pem
|
||||
$ NUM= the block's num you want to fetch
|
||||
$ peer channel fetch $NUM -o orderer.example.com:7050 -c businesschannel --tls $CORE_PEER_TLS_ENABLED --cafile $ORDERER_CA |xargs mv true businesschannel_$NUM.block
|
||||
$ peer channel fetch oldest -o orderer.example.com:7050 -c businesschannel --tls $CORE_PEER_TLS_ENABLED --cafile $ORDERER_CA |xargs mv true businesschannel_oldest.block
|
||||
$ peer channel fetch newest -o orderer.example.com:7050 -c businesschannel --tls $CORE_PEER_TLS_ENABLED --cafile $ORDERER_CA |xargs mv true businesschannel_newest.block
|
||||
```
|
||||
|
||||
temporarily cannot support specify self-defined-file.
|
||||
Loading…
Reference in New Issue