# Tools

# Interaction tools

Interact with your Hyperledger Fabric peer using the fabric-tools Docker container.

# Prerequisites

Install and run Docker.

# Connect to your peer

# Export the organization identity of your network

  1. On Chainstack, navigate to your vault.
  2. Select your Hyperledger Fabric identity issued by cryptogen.
  3. Click Export.

This will export the organization certificates in a ZIP archive. Unarchive the exported file.

Unarchiving the exported file will create a directory named after your organization's identity. For example, id-123-456-7.

# Export the orderer certificate of your network

  1. On Chainstack, navigate to your network.
  2. Select Service nodes > Orderer.
  3. Click Export.

This will export a ZIP with the following files:

  • The orderer certificate container in PEM.
  • The orderer connection profile in JSON.

Place the PEM certificate container in the directory that was created at the previous step when you unarchived the exported organization identity file.

# Run the fabric-tools Docker container

docker run -v /host/path/to/IDENTITY_DIRECTORY/:/MOUNT_DIRECTORY -it hyperledger/fabric-tools:2.2.0 /bin/ash

where

  • /host/path/to/IDENTITY_DIRECTORY/ — path to the directory with the organization identity that you exported at the previous step.
  • MOUNT_DIRECTORY — any name to mount a directory.

Example:

docker run -v /home/user/id-123-456-7/:/data -it hyperledger/fabric-tools:2.2.0 /bin/ash

# Provide connection details and certificate paths

In the running Docker container, provide the following:

export CORE_PEER_ADDRESS=PEER_RPC_ENDPOINT
export CORE_PEER_MSPCONFIGPATH=/MOUNT_DIRECTORY/msp/
export CORE_PEER_LOCALMSPID="MSP_ID"
export CORE_PEER_TLS_ENABLED=true
export CORE_PEER_TLS_ROOTCERT_FILE=/MOUNT_DIRECTORY/msp/tlscacerts/IDENTITY_CERTIFICATE
export ORDERER_CA=/MOUNT_DIRECTORY/ORDERER_CERTIFICATE
export ORDERER_ADDRESS=ORDERER_RPC_ENDPOINT

where

  • PEER_RPC_ENDPOINT — the RPC endpoint of your peer. On Chainstack, navigate to your peer; click Access and credentials > RPC endpoint.
  • MOUNT_DIRECTORY — the name of the directory that you mounted at the previous step.
  • MSP_ID — the ID of your organization. To get the ID, click your deployed network and then Details.
  • IDENTITY_CERTIFICATE — the identity certificate container file that is in the /msp/tlscacerts directory.
  • ORDERER_CERTIFICATE — the orderer certificate container file that you exported at a previous step.
  • ORDERER_RPC_ENDPOINT — the RPC endpoint of your orderer. On Chainstack, navigate to your network; click Service nodes > Orderer > RPC endpoint.

Example:

export CORE_PEER_ADDRESS=nd-123-456-789.rg-123-456.p2pify.com:7051
export CORE_PEER_MSPCONFIGPATH=/data/msp/
export CORE_PEER_LOCALMSPID="RG-123-456-MSP"
export CORE_PEER_TLS_ENABLED=true
export CORE_PEER_TLS_ROOTCERT_FILE=/data/msp/tlscacerts/tlsca.rg-123-456.p2pify.com-cert.pem
export ORDERER_CA=/data/nd-123-456-789-cert.pem
export ORDERER_ADDRESS=nd-123-456-789.rg-123-456.p2pify.com:7050

# Check your connection

peer channel list

Example:

$ peer channel list
2020-02-27 09:46:00.631 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
Channels peers has joined:
defaultchannel

# Interact with a chaincode

# Package chaincode

peer lifecycle chaincode package CHAINCODE_NAME.tar.gz --lang LANGUAGE --path CHAINCODE_SOURCE_PATH --label CHAINCODE_LABEL

where

  • CHAINCODE_NAME — name of your chaincode.
  • LANGUAGE — the programming language of your chaincode: node for JavaScript, golang for Go, java for Java.
  • CHAINCODE_SOURCE_PATH — path to your chaincode source files. The files must be in the directory you mounted earlier.
  • CHAINCODE_LABEL — any label you want to give to your chaincode; can be the same as the chaincode name.

This will package the chaincode and place it in the root of your mounted directory. Check that the packaged chaincode is created by doing ls.

Example:

$ peer lifecycle chaincode package fabcar.tar.gz --lang node --path /data/chaincode/fabcar/javascript/ --label fabcar
$ ls
bin  fabcar.tar.gz  src

# Install the chaincode on the peer you are connected to

peer lifecycle chaincode install CHAINCODE_NAME.tar.gz

where

  • CHAINCODE_NAME — name of your chaincode.

Example:

$ peer lifecycle chaincode install fabcar.tar.gz
2020-02-27 07:44:36.291 UTC [cli.lifecycle.chaincode] submitInstallProposal -> INFO 001 Installed remotely: response:<status:200 payload:"\nGfabcar:6ab145685b4602cf429f93536981ea3eab802369e6359fb841fb0a9bcd4a51fb\022\006fabcar" >
2020-02-27 07:44:36.291 UTC [cli.lifecycle.chaincode] submitInstallProposal -> INFO 002 Chaincode code package identifier: fabcar:6ab145685b4602cf429f93536981ea3eab802369e6359fb841fb0a9bcd4a51fb

# Check the chaincode installation

peer lifecycle chaincode queryinstalled

Example:

$ peer lifecycle chaincode queryinstalled
Installed chaincodes on peer:
Package ID: fabcar:6ab145685b4602cf429f93536981ea3eab802369e6359fb841fb0a9bcd4a51fb, Label: fabcar

# Download the installed chaincode

peer lifecycle chaincode getinstalledpackage --package-id PACKAGE_ID --peerAddresses $CORE_PEER_ADDRESS --tls --tlsRootCertFiles $CORE_PEER_TLS_ROOTCERT_FILE

where

  • PACKAGE_ID — the ID of your chaincode installed on the peer. You can get the ID by running peer lifecycle chaincode queryinstalled.

Example:

$ peer lifecycle chaincode getinstalledpackage --package-id fabcar:6ab145685b4602cf429f93536981ea3eab802369e6359fb841fb0a9bcd4a51fb --peerAddresses $CORE_PEER_ADDRESS --tls --tlsRootCertFiles $CORE_PEER_TLS_ROOTCERT_FILE
$ ls
bin  fabcar:6ab145685b4602cf429f93536981ea3eab802369e6359fb841fb0a9bcd4a51fb.tar.gz  src

# Approve the chaincode for your organization

The majority of organizations in the channel must agree to the parameters of the chaincode.

peer lifecycle chaincode approveformyorg --name CHAINCODE_NAME --package-id PACKAGE_ID -o $ORDERER_ADDRESS --tls --tlsRootCertFiles $CORE_PEER_TLS_ROOTCERT_FILE --cafile $ORDERER_CA --version CHAINCODE_VERSION --channelID CHANNEL_ID --sequence SEQUENCE_NUMBER --init-required --waitForEvent

where

  • CHAINCODE_NAME — name of your chaincode.
  • PACKAGE_ID — the ID of your chaincode installed on the peer. You can get the ID by running peer lifecycle chaincode queryinstalled.
  • CHAINCODE_VERSION — the version of your chaincode as specified in the source files of the chaincode.
  • CHANNEL_ID — use defaultchannel.
  • SEQUENCE_NUMBER — the number of times your chaincode has been defined. Use 1 for your first installation. If you later upgrade your chaincode, use 2 and so on.
  • --init-required — an optional parameter if your chaincode requires initialization.
  • --waitForEvent — an optional parameter to wait for the event from each peer that signifies that the transaction has been committed successfully.

Example:

$ peer lifecycle chaincode approveformyorg --name fabcar --package-id fabcar:6ab145685b4602cf429f93536981ea3eab802369e6359fb841fb0a9bcd4a51fb -o $ORDERER_ADDRESS --tls --tlsRootCertFiles $CORE_PEER_TLS_ROOTCERT_FILE --cafile $ORDERER_CA --version 1.0.0 --channelID defaultchannel --sequence 1 --init-required --waitForEvent
2020-02-27 07:45:27.742 UTC [chaincodeCmd] ClientWait -> INFO 001 txid [817547cebd7dd66084e7ff852ca8cac35d0c505416a7787ddd81947558280dc7] committed with status (VALID)

# Query the approved chaincode

peer lifecycle chaincode queryapproved --channelID CHANNEL_ID -n CHAINCODE_NAME

where

  • CHANNEL_ID — use defaultchannel.
  • CHAINCODE_NAME — name of your chaincode.

Example:

$ peer lifecycle chaincode queryapproved --channelID defaultchannel -n fabcar
Approved chaincode definition for chaincode 'fabcar' on channel 'defaultchannel':
sequence: 1, version: 1.0.0, init-required: true, package-id: fabcar:6ab145685b4602cf429f93536981ea3eab802369e6359fb841fb0a9bcd4a51fb, endorsement plugin: escc, validation plugin: vscc

# Check the chaincode commit readiness

peer lifecycle chaincode checkcommitreadiness -o $ORDERER_ADDRESS --channelID CHANNEL_ID --tls --cafile $ORDERER_CA --name CHAINCODE_NAME --version CHAINCODE_VERSION --init-required --sequence SEQUENCE_NUMBER

where

  • CHANNEL_ID — use defaultchannel.
  • CHAINCODE_NAME — name of your chaincode.
  • CHAINCODE_VERSION — the version of your chaincode as specified in the source files of the chaincode.
  • --init-required — an optional parameter if your chaincode requires initialization.
  • SEQUENCE_NUMBER — the number of times your chaincode has been defined.

Example:

$ peer lifecycle chaincode checkcommitreadiness -o $ORDERER_ADDRESS --channelID defaultchannel --tls --cafile $ORDERER_CA --name fabcar --version 1.0.0 --init-required --sequence 1
Chaincode definition for chaincode 'fabcar', version '1.0.0', sequence '1' on channel 'defaultchannel' approval status by org:
RG-123-456-MSP: true

# Commit the chaincode

peer lifecycle chaincode commit -o $ORDERER_ADDRESS --channelID CHANNEL_ID --name CHAINCODE_NAME --version CHAINCODE_VERSION --sequence SEQUENCE_NUMBER --init-required --tls --tlsRootCertFiles $CORE_PEER_TLS_ROOTCERT_FILE --cafile $ORDERER_CA --peerAddresses $CORE_PEER_ADDRESS

where

  • CHANNEL_ID — use defaultchannel.
  • CHAINCODE_NAME — name of your chaincode.
  • CHAINCODE_VERSION — the version of your chaincode as specified in the source files of the chaincode.
  • SEQUENCE_NUMBER — the number of times your chaincode has been defined. Use 1 for your first installation. If you later upgrade your chaincode, use 2 and so on.
  • --init-required — an optional parameter if your chaincode requires initialization.

Example:

$ peer lifecycle chaincode commit -o $ORDERER_ADDRESS --channelID defaultchannel --name fabcar --version 1.0.0 --sequence 1 --init-required --tls --tlsRootCertFiles $CORE_PEER_TLS_ROOTCERT_FILE --cafile $ORDERER_CA --peerAddresses $CORE_PEER_ADDRESS
2020-02-27 07:48:29.579 UTC [chaincodeCmd] ClientWait -> INFO 001 txid [df2ce4feadf60dea1d7969a59ef6c512e71334b2d56bd208e0c5980b7a19ee42] committed with status (VALID)

# Query the committed chaincode definitions

peer lifecycle chaincode querycommitted -o $ORDERER_ADDRESS --channelID CHANNEL_ID --tls --tlsRootCertFiles $CORE_PEER_TLS_ROOTCERT_FILE --cafile $ORDERER_CA

where

  • CHANNEL_ID — use defaultchannel.

Example:

$ peer lifecycle chaincode querycommitted -o $ORDERER_ADDRESS --channelID defaultchannel --tls --tlsRootCertFiles $CORE_PEER_TLS_ROOTCERT_FILE --cafile $ORDERER_CA
Committed chaincode definitions on channel 'defaultchannel':
Name: fabcar, Version: 1.0.0, Sequence: 1, Endorsement Plugin: escc, Validation Plugin: vscc

# Development tools

# Visual Studio Code

You can use the Hyperledger Fabric extension for VS Code with a Chainstack-deployed Hyperledger Fabric network.

# Prerequisites

# Export the identity

  1. Navigate to your Hyperledger Fabric network.
  2. Click Details.
  3. Select the identity in Admin identity.
  4. Click Export.

This will export the organization certificates in a ZIP archive. Unarchive the exported file.

# Export the network connection profile

  1. Navigate to your Hyperledger Fabric network.
  2. Click Details.
  3. Click Export connection profile.

This will export the network connection profile in JSON.

# Export the peer connection profile

  1. On Chainstack, navigate to your network and click your peer node.
  2. Next to Access and credentials, click Export.

This will export the peer connection profile in JSON.

# Export the orderer connection profile

  1. On Chainstack, navigate to your network.
  2. Select Service nodes > Orderer.
  3. Click Export.

This will export a ZIP archive with the following files:

  • The orderer certificate container in PEM.
  • The orderer connection profile in JSON.

You only need the orderer connection profile in JSON.

# Connect to the network in VS Code

  1. In VS Code, under Fabric environments, click the plus sign (+).
  2. Select Add any other Fabric network.
  3. Give any name to the network.
  4. Browse to the JSON connection profile for your peer node that you exported earlier.
  5. Click Done adding nodes.
  6. Under Other networks, click the peer node that you added.
  7. Click Add new wallet > Create new wallet.
  8. Give any name to the wallet.
  9. Click Add identity > Provide a JSON identity file from IBM Blockchain Platform.
  10. Browse for the identity.json file that is in the directory you unarchived when you exported the identity.
  11. Click Nodes > Import nodes.
  12. Browse to the JSON connection profile for your orderer node that exported earlier.
  13. Click Done adding nodes.
  14. Click the orderer node that you added and select the wallet and the identity that you created when setting up the peer node.

You can now connect to your Hyperledger Fabric network from VS Code and deploy chaincodes to it.

# Create a gateway to the network in VS Code

  1. In VS Code, under Fabric gateways, click the plus sign (+).
  2. Select one of the following options:
    • Create a gateway from a connection profile — select this option if you have not connected to the network as described in the previous section.
    • Create a gateway from a Fabric environment — select this option if you have connected to the network as described in the previous section. Then select the network. This will create the gateway.
  3. If you are creating the gateway from a connection profile, type in a name for the gateway and select the network connection profile that you exported previously.
  4. If you have a wallet created, associate an existing wallet with the gateway.
  5. If you do not have a wallet, under Fabric wallets, click the plus sign (+).
  6. Click Create a new wallet and add an identity. Give the wallet any name.
  7. Provide the MSP ID. To find the MSP ID, navigate to your Hyperledger Fabric network on Chainstack, click Details, copy the MSP ID value.
  8. Click Provide a JSON identity file from IBM Blockchain Platform.
  9. Browse for the identity.json file that is in the directory you unarchived when you exported the identity.
  10. Under Fabric gateways, right-click the gateway and select Associate a wallet. Associate the wallet that you created.

This will create the Hyperledger Fabric network gateway.