Testing a smart contract using a REST client

Up until this point, we have designed and developed our smart contract, deployed and installed it on all member peers, activated it on our channel, and exposed it to external applications by enabling the chaincode in the REST proxies of all members. Currently, we have five access points to the smart contract, one for each of the organizations in the network.

The two repair shops are still missing as entry points, as these existing, on-premises Hyperledger Fabric member organizations have not joined our business network yet. Either way, they would not have their own REST proxy as this is part of the OBCS offering.

These two organizations will need to use the SDK provided by Fabric to invoke the ...

Get Blockchain across Oracle now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.