We also need to install the chaincode on the OBCS instances of the other members, since for members to endorse transactions produced by the chaincode invocation of other members, they need to execute the transaction redundantly on their own nodes. But before we do that, let's activate the chaincode on the channel and give permission to other members to configure the REST proxy and execute the transactions exposed by the chaincode.
Let's pick up where we left off a moment ago. Click on the Instantiated on Channels menu item on the left to navigate to that section. The page now shows a list of channels on which the chaincode is active. Of course, this list is currently empty, as we haven't yet activated ...
