Enable a Chaincode in a REST Proxy

You can enable a chaincode in the REST proxy if you want to use the REST proxy to interact and process ledger transactions with the Oracle Blockchain REST APIs rather that the native Hyperledger Fabric APIs.

You must have instantiated the chaincode before you can enable it in the REST proxy. See Instantiate a Chaincode.
You must be an administrator to perform this task.
  1. Go to the console and select the Chaincodes tab.
  2. In the chaincode table, locate the top-level entry for the chaincode that you want to enable. Click More Actions and select Enable in REST Proxy. Note that only the chaincodes that have been instantiated display the More Actions menu.
    The Enable Chaincode in REST Proxy page is displayed.
  3. Select one or more REST proxies that you want to enable the chaincode in. Your instance contains four REST proxy nodes to allow you to balance the workload across the REST proxy nodes as needed by your network.
  4. In the Channel field, select a channel that the chaincode was instantiated on.
  5. In the Endorse Peers field, select one or more peers required to endorse the chaincode transactions. The peers that display in this list are the peers that have the chaincode installed on them and that are joined to the channel you selected. If your chaincode is using an endorsement policy, then the number of peers you select must comply with the policy.
    Oracle suggests that you choose peers from each partition for the purposes of resiliency and high availability. For example, if you’re using the default endorsement policy, it requires an endorsement from any peer on the network. In the Endorse Peers field you should select one peer from each partition so that if one peer is down, the other peer can perform the endorsement, and if one of the partitions is either slow or not running, then the required endorsement can still be gotten.
  6. Click Submit.