Skip to content

Latest commit

 

History

History
76 lines (57 loc) · 4.38 KB

install_chaincode.md

File metadata and controls

76 lines (57 loc) · 4.38 KB
Raw

Install and Instantiate Chaincode w/IBM Cloud

  1. If you are not currently on the Blockchain "Resources" page... then get there via:

    1. Login to IBM Cloud
    2. Get to your dashboard by clicking the "Menu" icon on the top left and then clicking the "Dashboard" link
    3. Under "All Services" locate your the Blockchain row and click it
    4. Enter your IBM Blockchain Service's dashboard by clicking the "Enter" button

  2. If you are on the "Overview" page already, then click the "Install code" link on the left navigation

  • Select 1 of your peers in the drop down
  • Now click the "Install Chaincode" button

  • Fill out the chaincode name as "marbles" (note this could be whatever you want to use to identify the chaincode)
  • Fill out the chaincode version as "v5" (note this could be whatever you want to identify which chaincode version)
  • Select the "Choose Files" button and select all the files found in <marbles directory>/chaincode/src/marbles
    • Alternatively you can zip up the .go files and submit a single zip file
  • Click "Submit"

  • Great, so you should see marbles listed in the chaincode table for this peer.
  • All we've done so far is upload the files on to the peer. Next, we need to tell it what channel to run on.
  • Click the 3 dots in the "ACTIONS" column to open the actions menu. Then click "Instantiate".

  • The arguments input box is for entering the arguments we want to pass to our chaincode's Init() function.
    • Typically, this is an array of strings. As you type you can see exactly what will be sent in the lower input named "Chaincode Arguments".
  • Marbles chaincode is expecting a single numeric input argument. Therefore, enter your favorite number. Mines 314.
    • Marbles chaincode will store this number to the ledger as a self-test of sorts. It can literally be any number you want.
  • Next from the "Channel" drop down, select our 1 and only channel defaultchannel
  • Then click the "Submit" button

  • Next up is the chaincode policy. The "Simple Policy" allows us to set the number of endorsements for a chaincode invocation. If we choose the simple policy and set the signatures to 2 then we would need 2 members to sign every invocation. Only have 1 signature would would fail. However if we set the signatures to 1 then any member's signature will do. This is the policy type we should use. (The advanced policy allows us to write the policy using fabric syntax/notation. This is beyond the scope of marbles, but it would allow us to dictate who can endorse chaincode invocations)

    • Select the "Simple Policy"
    • Set the "Endorsement Policy" number to 1 (this is the number of required signatures)
    • Click the "Submit" button

  • If it went well the chaincode page will refresh

  • Now that the chaincode has been instantiated on the channel, let's look at it

  • Click the "Channels" link on the left navigation

  • Click the channel you instantiated marbles on

  • Click the "Chaincode" sub-tab

  • On this panel, you should see something similar to the picture above. Marbles is instantiated on at least one peer
  • Expand the row to see which peer
  • Click the log button to see if marbles started up. You should log messages like:
    Marbles Is Starting Up
    Init() args count: 1
    Init() args found: [314]
    Init() arg[0] length 3
    args[0] is not empty, must be instantiating
     - ready for action
  • The last thing we need to do is grab all the service instance's credentials for our network. We will use this data to inform the marbles node.js application of our blockchain's networking addresses and credentials.
  • Get the service credentials by clicking the "JSON" button under the "App Integration" column (you may need to expand the chaincode row first)
  • Important: This will open the JSON in your browser. Copy this data and save/replace the entire contents of the file <marbles directory>/config/connection_profile_tls.json
    • This JSON contains all the details needed to connect to your network.
    • Marbles will read this file to connect and transact on your network on this channel.

Finish Up

Congrats! The network is all setup and marbles chaincode is running.

  • Continue where you left off in the tutorial.