...
- Each organizational user installs the chain code on their respective nodes.
- To install any available chaincode onto your nodes, click the "Install" button. A pop-up window will appear, allowing you to select the desired nodes within your organization for installation.
By default, the nodes you have already installed will be automatically selected, and cannot be unchecked.
Step 4: Approve chaincode
- Each organization performs licensing operations on the chaincode.
- Click the Approve button to approve chaincode and check other organizations' approvement status.
- You can check the organizations that have already approved the current chaincode and perform licensing operations if desired.
4. The corresponding approve button will disappear after you approved the chaincode.
- need to specify which channel to approve, the name for the approved cc and specify whether the chaincode requires invoking 'init'.
Step 5: Commit chaincode
- You can commit the chaincode to channels by clicking Commit buttonYou can check chaincode commit policies before committing by clicking the link in pop-up window
- You need to choose the desired channel for committing the chaincode from the available options in the drop-down menu. You can also review the list of channels where the chaincode has already been committed.
- Specify whether the chaincode requires invoking 'init' by checking/unchecking the checkbox.
4. If the current approvement does not meet the channel policies, commitment may fail and you will see a prompt window
...
- Click any row on the chaincode table, you will enter the sub-detail page, which shows all information about current cc, including namePackageID, version, language, sha256sum, description and peer nodes the cc is installed.
- The frontend page is routing using chaincode name, the following page uses the URL path hostname/operatorchaincodeDefinition/chaincode/cc1 (we can also use id for routing)packageID/detail
More operations(optional):
...