* Return exit(1) if application-java fails If application-java fails, return an exit(1) code, so that callers such as Github Actions CI can detect the failure. Signed-off-by: David Enyeart <enyeart@us.ibm.com> * asset-transfer-basic CI improvements - Application failure should result in CI failure - Automatically remove wallet from prior runs - Fix chaincode name issues, allow chaincode name to be passed from CI - Fix appUser collisions (duplicate registration failures) - Fix key create collisions across apps (in cases where same chaincode is used for multiple apps) Signed-off-by: David Enyeart <enyeart@us.ibm.com> --------- Signed-off-by: David Enyeart <enyeart@us.ibm.com> |
||
|---|---|---|
| .. | ||
| application-gateway-go | ||
| application-gateway-java | ||
| application-gateway-typescript | ||
| application-go | ||
| application-java | ||
| application-javascript | ||
| application-typescript | ||
| application-typescript-hsm | ||
| chaincode-external | ||
| chaincode-go | ||
| chaincode-java | ||
| chaincode-javascript | ||
| chaincode-typescript | ||
| rest-api-go | ||
| rest-api-typescript | ||
| .gitignore | ||
| README.md | ||
Asset transfer basic sample
The asset transfer basic sample demonstrates:
- Connecting a client application to a Fabric blockchain network.
- Submitting smart contract transactions to update ledger state.
- Evaluating smart contract transactions to query ledger state.
- Handling errors in transaction invocation.
About the sample
This sample includes smart contract and application code in multiple languages. This sample shows create, read, update, transfer and delete of an asset.
For a more detailed walk-through of the application code and client API usage, refer to the Running a Fabric Application tutorial in the main Hyperledger Fabric documentation.
Application
Follow the execution flow in the client application code, and corresponding output on running the application. Pay attention to the sequence of:
- Transaction invocations (console output like "--> Submit Transaction" and "--> Evaluate Transaction").
- Results returned by transactions (console output like "*** Result").
Smart Contract
The smart contract (in folder chaincode-xyz) implements the following functions to support the application:
- CreateAsset
- ReadAsset
- UpdateAsset
- DeleteAsset
- TransferAsset
Note that the asset transfer implemented by the smart contract is a simplified scenario, without ownership validation, meant only to demonstrate how to invoke transactions.
Running the sample
The Fabric test network is used to deploy and run this sample. Follow these steps in order:
-
Create the test network and a channel (from the
test-networkfolder)../network.sh up createChannel -c mychannel -ca -
Deploy one of the smart contract implementations (from the
test-networkfolder).# To deploy the TypeScript chaincode implementation ./network.sh deployCC -ccn basic -ccp ../asset-transfer-basic/chaincode-typescript/ -ccl typescript # To deploy the Go chaincode implementation ./network.sh deployCC -ccn basic -ccp ../asset-transfer-basic/chaincode-go/ -ccl go # To deploy the Java chaincode implementation ./network.sh deployCC -ccn basic -ccp ../asset-transfer-basic/chaincode-java/ -ccl java -
Run the application (from the
asset-transfer-basicfolder).# To run the Typescript sample application cd application-gateway-typescript npm install npm start # To run the Go sample application cd application-gateway-go go run . # To run the Java sample application cd application-gateway-java ./gradlew run
Clean up
When you are finished, you can bring down the test network (from the test-network folder). The command will remove all the nodes of the test network, and delete any ledger data that you created.
./network.sh down